A network technician is investigating a report that a client computer cannot access internal corporate resources using hostnames. Place the following troubleshooting steps in the correct logical sequence to systematically isolate and resolve the name resolution issue, from basic stack verification to cache remediation.
- 1Ping the loopback address () to verify that the local TCP/IP protocol stack is operating correctly.
- 2Run `ipconfig /all` to inspect the local network configuration and verify the assigned DNS server IP addresses.
- 3Ping the configured primary DNS server IP address to confirm Layer 3 network reachability.
- 4Execute an `nslookup` query targeting the hostname to test DNS service responsiveness on UDP/TCP port 53.
- 5Run `ipconfig /flushdns` to clear outdated or corrupted entries from the local DNS client resolver cache.
Answer
The correct logical sequence for troubleshooting DNS name resolution issues is: 1) Ping loopback address (127.0.0.1), 2) Run ipconfig /all to check DNS server configurations, 3) Ping primary DNS server IP, 4) Execute nslookup targeting hostname, 5) Run ipconfig /flushdns.
The standard network troubleshooting methodology progresses from local hardware/stack verification up to higher-level service queries and cache remediation. Verifying the loopback adapter establishes local TCP/IP operational status. Checking network configuration via `ipconfig /all` identifies target DNS server IP addresses. Pinging the DNS server tests Layer 3 reachability. Using `nslookup` isolates Application layer (DNS port 53) functionality. Finally, clearing the client resolver cache with `ipconfig /flushdns` resolves stale mapping issues on the workstation.
Step-by-Step Solution
Key Concept
Systematic OSI Bottom-Up / Layered Network Troubleshooting for Name Resolution
Estimated Time:1m 30s