A systems engineer is troubleshooting connectivity to a critical database server named `db1.internal.net`. Standard network utilities produce conflicting IP resolution results as shown below:
text
$ host db1.internal.net
db1.internal.net has address 192.168.1.50
$ dig @10.0.0.53 db1.internal.net +short
10.0.0.150
Which of the following is the most likely cause of this address discrepancy?
- A static entry in the local system HOSTS file is overriding standard DNS server resolution.Cevap
- BThe authoritative DNS server at 10.0.0.53 is serving stale cached records due to an expired TTL.
- COutbound TCP port 53 is blocked by a local host firewall rule on the client workstation.
- DThe DNS server is missing a valid reverse lookup PTR record for host db1.internal.net.
Cevap
A static entry in the local system HOSTS file is overriding standard DNS server resolution.
In standard operating system TCP/IP stacks, local name resolution precedence checks local static files (such as `/etc/hosts` on Linux or `hosts` on Windows) before issuing queries to configured DNS servers. When standard lookup utilities yield a different result than an explicit, direct query to the authoritative DNS server, a static mapping in the local HOSTS file is overriding the network DNS response.
Adım Adım Çözüm
Anahtar Kavram
Operating System Name Resolution Precedence (HOSTS file vs. DNS Server)