TELEMETRY // Normal: `nslookup` returns authoritative IP in <100 ms | Fault: `nslookup` returns Non-existent domain or timeout; `ipconfig /displaydns` shows stale entries
Why It Happens: Windows maintains a local DNS cache to speed up repeated lookups. If a domain's IP address changed or a previous lookup failed and was cached negatively, the resolver returns NXDOMAIN without querying the network, causing browsers to report DNS_PROBE_FINISHED_NXDOMAIN even though the domain is live.
Fast Verification Test: Open Command Prompt as Administrator and run `ipconfig /flushdns`, then immediately run `nslookup example.com`. If resolution succeeds after flushing, the cache was the root cause.
Tools Needed: Command Prompt (Administrator)
- Open Start, type cmd, right-click Command Prompt, and select Run as Administrator.
- Type `ipconfig /flushdns` and press Enter; confirm the message "Successfully flushed the DNS Resolver Cache."
- Type `ipconfig /registerdns` and press Enter to re-register the machine's DNS records.
- Restart the browser and test the previously failing domain.
⚠️ Safety Boundary: No electrical hazard; this is a software-only network stack operation.
TELEMETRY // Normal: IPv4 DNS set to Obtain automatically or valid resolver (e.g., 8.8.8.8) | Fault: Preferred DNS server blank, 0.0.0.0, or unreachable IP; IPv6 unchecked while IPv4 DNS missing
Why It Happens: Windows sends DNS queries to the configured DNS server addresses in the network adapter properties. If those addresses are invalid, unreachable, or the ISP's DNS server is down, the resolver receives no valid answer and returns NXDOMAIN to the browser.
Fast Verification Test: Run `nslookup example.com 8.8.8.8` in Command Prompt. If it resolves using Google's public DNS but fails with the default server, your configured DNS server addresses are incorrect.
Tools Needed: Network Connections control panel (ncpa.cpl)
- Press Win + R, type `ncpa.cpl`, and press Enter.
- Right-click your active Ethernet or Wi-Fi adapter and select Properties.
- Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
- Select "Use the following DNS server addresses" and enter Preferred: 8.8.8.8, Alternate: 8.8.4.4.
- Click OK, close all dialogs, and test web browsing.
⚠️ Safety Boundary: No electrical hazard; changing DNS settings only affects name resolution and is fully reversible.
TELEMETRY // Normal: `C:\Windows\System32\drivers\etc\hosts` contains only comments or localhost entries | Fault: A line maps the failing domain to 127.0.0.1, 0.0.0.0, or an invalid IP
Why It Happens: The Windows hosts file is checked before DNS servers. If malware, ad-blocking software, or a manual edit added a line pointing the target domain to a non-routable or dead IP, Windows immediately returns NXDOMAIN without ever contacting a DNS server.
Fast Verification Test: Open Notepad as Administrator, open `C:\Windows\System32\drivers\etc\hosts`, and search for the failing domain. If a line exists referencing it, the hosts file is overriding DNS.
Tools Needed: Notepad (Administrator) • File Explorer
- Open Start, type Notepad, right-click it, and select Run as Administrator.
- In Notepad, click File > Open and navigate to `C:\Windows\System32\drivers\etc\`.
- Change the file filter to "All Files" and select `hosts`.
- Delete any line containing the failing domain (unless you intentionally added it).
- Save the file, flush DNS with `ipconfig /flushdns`, and retest.
⚠️ Safety Boundary: Editing the hosts file requires Administrator privileges; incorrect edits can block legitimate websites but are reversible by restoring the file.
TELEMETRY // Normal: `services.msc` shows DNS Client service status = Running, startup type = Automatic | Fault: Service is Stopped or startup type is Disabled
Why It Happens: The DNS Client service (Dnscache) handles DNS name resolution and caching for Windows applications. If this service is stopped or disabled, browsers and other apps cannot resolve hostnames, producing DNS_PROBE_FINISHED_NXDOMAIN across all applications.
Fast Verification Test: Press Win + R, type `services.msc`, locate "DNS Client", and check that Status is Running and Startup type is Automatic. If stopped, right-click and select Start.
Tools Needed: Services console (services.msc)
- Press Win + R, type `services.msc`, and press Enter.
- Scroll to "DNS Client" in the list.
- Right-click DNS Client and select Properties.
- Set Startup type to Automatic and click Start if the service is stopped.
- Click Apply and OK, then restart the browser and test.
⚠️ Safety Boundary: No electrical hazard; modifying system services is safe but should be done with care to avoid disabling other critical Windows components.