A network administrator is troubleshooting a user workstation that cannot connect to an internal website named `server1.corp.local`. The technician runs the `nslookup` command on the workstation and receives the following output:
C:\Users\User> nslookup server1.corp.local
Server: dc01.corp.local
Address: 10.0.0.10
*** dc01.corp.local can't find server1.corp.local: Non-existent domain
Which of the following is the most likely cause of this name resolution failure?
- The host name `server1.corp.local` does not have a corresponding A record configured on the DNS server.Answer
- BThe DNS server at 10.0.0.10 is offline and failing to receive UDP port 53 network traffic.
- CThe workstation is misconfigured to send standard DNS client queries over TCP instead of UDP.
- DThe DNS server requires an MX record rather than an A record for IPv4 internal host resolution.
Answer
The host name does not have a corresponding A record configured on the DNS server.
The output explicitly demonstrates that the client reached the DNS server at `10.0.0.10`, which answered with a 'Non-existent domain' (NXDOMAIN) status. This indicates that the DNS server is working correctly but lacks an A record mapping `server1.corp.local` to an IP address.
Step-by-Step Solution
Key Concept
DNS Host Record (A Record) Verification and NXDOMAIN Error Diagnosis