A network technician receives reports that client workstations on a corporate subnet are unable to resolve external internet hostnames, although internal hostname resolution functions normally. Place the diagnostic and remediation steps in the correct logical sequence from initial client-side isolation to final resolution verification.
- 1Verify layer 3 IP connectivity from the client workstation to the designated internal DNS server.
- 2Execute an `nslookup` command targeting the internal DNS server to query an external domain name.
- 3Execute an `nslookup` command specifying an external public DNS server to test outbound DNS connectivity.
- 4Reconfigure the internal DNS server's conditional forwarders and confirm firewall rules allow outbound traffic on port .
- 5Flush the local client DNS cache using `ipconfig /flushdns` and test external domain name resolution.
Cevap
The correct sequence begins with verifying network connectivity to the internal DNS server, testing recursive lookup failure on the local resolver, testing direct outbound lookup to a public DNS server, remediating server forwarder and firewall settings, and finally flushing the local client cache to verify resolution.
Effective troubleshooting follows a logical progression from local connectivity verification to service isolation, root-cause remediation, and end-state validation. Verifying network layer reachability first ensures the client can reach its assigned resolver. Testing queries against the internal DNS server isolates recursion failures. Testing queries directly against an external public resolver determines if outbound transport on port is blocked. Fixing the forwarders/firewall addresses the root cause, and flushing the client cache verifies successful end-to-end resolution.
Adım Adım Çözüm
Anahtar Kavram
Systematic DNS Troubleshooting Methodology for External Resolution and Upstream Forwarder Failures
Tahmini Süre:1m 30s