# Fix DNS_PROBE_FINISHED_NXDOMAIN on Windows 11
Canonical Interactive Tool: https://www.whyitsbroken.com/fix/fix-dns-probe-finished-nxdomain-on-windows-11
Error Code: `DNS_PROBE_FINISHED_NXDOMAIN`
Subsystem: Windows 11 TCP/IP DNS Client & Resolver Stack | Difficulty: Easy DIY | Time: 15-45 min | DIY Cost: $0.00-$45.00 (vs Pro $150.00-$340.00)
Empirical Verified Fixes: 1 | Evolution Version: v1

## Direct Answer Summary
The most probable root cause is a stale Windows DNS resolver cache or manually overridden DNS server settings returning NXDOMAIN. Confirm in under 5 minutes by opening Command Prompt and running `nslookup example.com`; if it fails but `nslookup example.com 8.8.8.8` succeeds, your system DNS is misconfigured. DIY fix costs $0 using built-in Windows tools; pro network service typically costs $150-$340.

## Ranked Root Causes & Telemetry Signatures
### 1. Stale or Corrupt Windows DNS Resolver Cache (Baseline Probability: 35%)
- **Telemetry Signature:** 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.
- **60-Second 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.
- **Resolution Steps:**
  1. Open Start, type cmd, right-click Command Prompt, and select Run as Administrator.
  2. Type `ipconfig /flushdns` and press Enter; confirm the message "Successfully flushed the DNS Resolver Cache."
  3. Type `ipconfig /registerdns` and press Enter to re-register the machine's DNS records.
  4. Restart the browser and test the previously failing domain.

### 2. Misconfigured or Unresponsive DNS Server Addresses (Baseline Probability: 30%)
- **Telemetry Signature:** 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.
- **60-Second 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.
- **Resolution Steps:**
  1. Press Win + R, type `ncpa.cpl`, and press Enter.
  2. Right-click your active Ethernet or Wi-Fi adapter and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Select "Use the following DNS server addresses" and enter Preferred: 8.8.8.8, Alternate: 8.8.4.4.
  5. Click OK, close all dialogs, and test web browsing.

### 3. Malicious or Stale Entries in Windows Hosts File (Baseline Probability: 20%)
- **Telemetry Signature:** 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.
- **60-Second 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.
- **Resolution Steps:**
  1. Open Start, type Notepad, right-click it, and select Run as Administrator.
  2. In Notepad, click File > Open and navigate to `C:\Windows\System32\drivers\etc\`.
  3. Change the file filter to "All Files" and select `hosts`.
  4. Delete any line containing the failing domain (unless you intentionally added it).
  5. Save the file, flush DNS with `ipconfig /flushdns`, and retest.

### 4. DNS Client Service Stopped or Disabled (Baseline Probability: 15%)
- **Telemetry Signature:** 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.
- **60-Second 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.
- **Resolution Steps:**
  1. Press Win + R, type `services.msc`, and press Enter.
  2. Scroll to "DNS Client" in the list.
  3. Right-click DNS Client and select Properties.
  4. Set Startup type to Automatic and click Start if the service is stopped.
  5. Click Apply and OK, then restart the browser and test.

## Frequently Asked Questions
**Q: Why does DNS_PROBE_FINISHED_NXDOMAIN happen only in Chrome but not Edge?**
Chrome maintains its own internal DNS cache at chrome://net-internals/#dns. Clear it there, or the browser may be using a different DNS-over-HTTPs setting than the system resolver.

**Q: Will changing my DNS to 8.8.8.8 slow down my internet?**
No. DNS only affects the initial domain lookup, not download speed. Public resolvers like Google (8.8.8.8) or Cloudflare (1.1.1.1) are often faster than ISP DNS.

**Q: Can a VPN cause DNS_PROBE_FINISHED_NXDOMAIN?**
Yes. Some VPNs push their own DNS servers that may be unreachable or misconfigured. Disconnect the VPN and test, or disable IPv6 in the adapter properties if the VPN tunnel conflicts with IPv4 DNS.

**Q: Is editing the hosts file safe on Windows 11?**
Yes, as long as you run Notepad as Administrator and only remove lines you did not intentionally add. Always keep a backup copy before making changes.

## External Technical References
- [Fix dns_probe_finished_nxdomain Error Fast (2026 Guide)](https://www.hostaccent.com/blog/fix-dns-probe-finished-nxdomain)
- [Just trying to fix this issue i have DNS_PROBE_FINISHED_NXDOMAIN - Microsoft Q&A](https://learn.microsoft.com/en-us/answers/questions/2394431/just-trying-to-fix-this-issue-i-have-dns-probe-fin)
- [I keep getting DNS_PROBE_FINISHED_NXDOMAIN - Google Chrome Community](https://support.google.com/chrome/thread/283759045/i-keep-getting-dns-probe-finished-nxdomain?hl=en)
- [Easily Fix DNS_PROBE_FINISHED_NXDOMAIN Error in Chrome](https://www.youtube.com/watch?v=70QILplfyfA)
- [DNS_PROBE_FINISHED_NXDOMAIN / domain cannot resolve - Application Performance / DNS & Network - Cloudflare Community](https://community.cloudflare.com/t/dns-probe-finished-nxdomain-domain-cannot-resolve/587292)
