A workstation on an enterprise network cannot connect to an internal intranet portal by its hostname `portal.local`. A network technician must execute a systematic diagnostic process to isolate whether the issue originates from local client caching, the default DNS resolver, or the authoritative DNS server configuration. In what order should the technician execute the following troubleshooting steps?
- 1Inspect the workstation's local resolver cache using `ipconfig /displaydns` to verify existing hostname-to-IP entries.
- 2Purge potentially invalid local entries from memory by running `ipconfig /flushdns`.
- 3Execute `nslookup portal.local` to test query resolution against the client's configured default DNS server.
- 4Execute `nslookup portal.local 10.10.10.10` explicitly targeting the authoritative internal DNS server.
Cevap
The correct sequence begins with inspecting the local cache (`ipconfig /displaydns`), flushing stale entries (`ipconfig /flushdns`), testing standard resolution against the default server (`nslookup portal.local`), and finally querying the authoritative DNS server directly (`nslookup portal.local 10.10.10.10`).
The correct order follows standardCompTIA troubleshooting methodology: non-destructive inspection of local client cache (`ipconfig /displaydns`), clearing stale local data (`ipconfig /flushdns`), testing normal client DNS query behavior (`nslookup portal.local`), and isolating infrastructure components by directly querying the authoritative server (`nslookup portal.local 10.10.10.10`).
Adım Adım Çözüm
Anahtar Kavram
Systematic DNS Troubleshooting Methodology