A network engineer is systematically troubleshooting a client workstation that is experiencing intermittent domain name resolution failures for internal corporate servers. Arrange the troubleshooting steps in the correct, logical order—beginning with local client configuration verification and progressing outward to network transport validation.
- 1Run ipconfig /all to verify the client's assigned Primary DNS server IP address and configured DNS suffix search list.
- 2Examine local cached resolution records using ipconfig /displaydns to check for stale, corrupted, or erroneous entries.
- 3Inspect the local HOSTS file (%SystemRoot%\System32\drivers\etc\hosts) to check for static mapping overrides.
- 4Perform an explicit DNS query using nslookup directed explicitly to the designated internal DNS server IP to bypass local OS caching.
- 5Analyze network path ACLs and firewall rules to verify that traffic on UDP port 53 and TCP port 53 is not being blocked between the client and DNS server.
Answer
The correct systematic order begins with verifying client IP configuration settings (ipconfig /all), followed by inspecting local DNS cache entries (ipconfig /displaydns), checking static mapping overrides in the HOSTS file, issuing an explicit query directly to the DNS server (nslookup), and finally inspecting network path firewalls for UDP/TCP port 53 traffic blocking.
Systematic DNS troubleshooting follows a logical progression from local client endpoint configuration (verifying IP settings, clearing local cache, inspecting static HOSTS file entries) to direct server querying (nslookup), and finally to network path transport verification (UDP/TCP port 53 firewall inspection).
Step-by-Step Solution
Key Concept
Troubleshooting DNS and Name Resolution Services
Estimated Time:2m 0s