A technician is troubleshooting a network where users can access the internet but cannot reach a specific internal web server by its hostname. The server's IP is 10.0.0.5, and pinging 10.0.0.5 works. The technician checks the DNS server and finds an A record for the server's name pointing to 10.0.0.10. What is the most likely issue?
Trap 1: The DHCP server assigned the wrong IP to the server
The server's IP is 10.0.0.5 and is reachable; DHCP assignment is not the problem since the server is working.
Trap 2: The router's port forwarding is misconfigured
Port forwarding is for external access; internal users don't use it, and the server is reachable by IP.
Trap 3: The server's firewall is blocking DNS queries
DNS queries go to the DNS server, not the web server; the server's firewall wouldn't affect hostname resolution.
- A
The DHCP server assigned the wrong IP to the server
Why wrong: The server's IP is 10.0.0.5 and is reachable; DHCP assignment is not the problem since the server is working.
- B
The DNS A record is incorrect
The A record points to 10.0.0.10 instead of 10.0.0.5, so DNS resolves to the wrong IP, preventing access by hostname.
- C
The router's port forwarding is misconfigured
Why wrong: Port forwarding is for external access; internal users don't use it, and the server is reachable by IP.
- D
The server's firewall is blocking DNS queries
Why wrong: DNS queries go to the DNS server, not the web server; the server's firewall wouldn't affect hostname resolution.