• August 19, 2026
  • 0 Comments

DNS_PROBE_FINISHED_NXDOMAIN means your browser asked a DNS server to translate a website’s name into an IP address, and the server replied “this domain doesn’t exist.” It’s almost always fixable in under 5 minutes by flushing your DNS cache, switching to a public DNS server like 8.8.8.8, or restarting your router. It’s rarely a sign your device is broken — it’s a DNS lookup failing somewhere between your browser and the internet.

What Is DNS_PROBE_FINISHED_NXDOMAIN?

DNS_PROBE_FINISHED_NXDOMAIN is a Chrome (and Chromium-browser) error that shows up as “This site can’t be reached.” NXDOMAIN is short for Non-Existent Domain — it’s the technical response a DNS server sends when it cannot find any record for the domain you typed.

Think of DNS (Domain Name System) as the internet’s phonebook. When you type a URL, your browser asks a DNS server, “What’s the IP address for this name?” NXDOMAIN means the server checked its phonebook and found nothing — either because the domain genuinely doesn’t exist, or because something between your device and the DNS server is broken.

What Causes This Error?

Before jumping into fixes, it helps to know the usual culprits:

  • Local DNS cache is outdated or corrupted — your device remembers an old, wrong record.
  • Your DNS server is down or slow — often your ISP’s default DNS.
  • Typo in the URL — the simplest cause, and worth a second glance first.
  • VPN or proxy interference — routes your DNS requests somewhere broken.
  • Router or modem glitch — needs a reboot to clear its own DNS cache.
  • Corrupted network settings (Winsock/TCP-IP stack on Windows).
  • A bad entry in your hosts file blocking the domain.
  • Antivirus or firewall software intercepting DNS traffic.
  • Outdated network drivers.

Now, the fixes — ordered from fastest to most involved.

How Do You Fix DNS_PROBE_FINISHED_NXDOMAIN?

1. Flush Your DNS Cache

Your computer stores DNS lookups locally to save time. If that cache holds a bad record, every request fails until you clear it.

Windows:

ipconfig /flushdns

Run this in Command Prompt (as Administrator).

Mac:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Run in Terminal.

This alone fixes the error a large share of the time — always try it first.

2. Switch to a Public DNS Server (Google or Cloudflare)

If your ISP’s DNS server is slow or down, switching fixes it instantly.

  • Google Public DNS: 8.8.8.8 and 8.8.4.4
  • Cloudflare DNS: 1.1.1.1 and 1.0.0.1

On Windows: Control Panel → Network and Sharing Center → Change adapter settings → right-click your connection → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → enter the DNS addresses manually.

On Mac: System Settings → Network → Wi-Fi → Details → DNS → add the addresses.

Cloudflare’s 1.1.1.1 is generally the fastest option and prioritizes privacy; Google’s 8.8.8.8 is the most widely tested and reliable for compatibility.

3. Clear Chrome’s Host Cache

Chrome keeps its own separate DNS cache from your OS.

Go to chrome://net-internals/#dns and click Clear host cache. Also visit chrome://net-internals/#sockets and click Flush socket pools. Restart Chrome afterward.

4. Disable VPN or Proxy Temporarily

VPNs and proxies reroute your DNS requests through their own servers. If that server is misconfigured or overloaded, you’ll get NXDOMAIN even though the site is fine.

Turn off your VPN or proxy extension, then reload the page. If it works, the VPN’s DNS handling — not your internet — was the problem. Most VPN apps let you set a custom DNS server in their settings if you want to keep using the VPN.

5. Restart Your Router and Modem

Routers cache DNS too, and that cache can go stale just like your computer’s. Unplug both the router and modem, wait 30 seconds, plug the modem back in first, then the router. This clears the router’s DNS cache and often resolves the issue network-wide — useful if the error is affecting multiple devices in your home or office.

6. Reset TCP/IP and Winsock (Windows)

If your network stack itself is corrupted, DNS lookups fail regardless of which server you use. In an elevated Command Prompt, run:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your computer after running these.

7. Check Your Hosts File for Bad Entries

The hosts file overrides DNS for specific domains — malware or a leftover entry from old dev work can silently block a site.

  • Windows path: C:\Windows\System32\drivers\etc\hosts
  • Mac/Linux path: /etc/hosts

Open it in a text editor (as Administrator/root) and look for any line referencing the domain that’s failing. Delete or comment it out with a #, save, and flush DNS again.

8. Temporarily Disable Antivirus or Firewall

Some security software includes DNS filtering or “safe browsing” features that misidentify legitimate sites. Disable your antivirus and firewall for a minute and reload the page. If it loads, check your antivirus’s web-protection or DNS-filtering settings rather than leaving protection off — whitelist the domain instead.

9. Update or Reinstall Network Drivers

Outdated network adapter drivers can corrupt DNS requests before they even leave your device. On Windows: Device Manager → Network Adapters → right-click your adapter → Update driver. On Mac, this is handled through macOS system updates. If updating doesn’t help, uninstalling and letting Windows reinstall the driver on reboot often clears deeper corruption.

10. Test on Another Device or Network

This isolates whether the issue is your device, your network, or the website itself. Try the same URL on your phone using mobile data (not Wi-Fi). If it loads fine there, the problem is local to your original device or router. If it fails everywhere, the domain or its DNS records are genuinely broken.

Is the Problem on Your End or the Website’s?

This matters most if you’re a freelancer or business owner and a client says “your site is down.”

  • Only you see the error, on one device: local DNS/cache issue — fixes #1, #3, #6 apply.
  • Everyone on your network sees it: router/ISP DNS issue — fixes #2, #5 apply.
  • It fails on mobile data too, from multiple locations: the domain’s DNS records are likely misconfigured at the registrar or hosting level — this isn’t a browser fix, it needs a DNS/hosting check on the site’s end.

A fast way to confirm: check the site on downforeveryoneorjustme.com or run nslookup yourdomain.com in a terminal. If nslookup returns “Non-existent domain,” the DNS record itself is broken — that’s a hosting/registrar issue, not something the visitor can fix.

FAQs

What does NXDOMAIN actually mean?

NXDOMAIN is the DNS server’s way of saying “no record exists for this domain name.” It’s a standard DNS response code, not a Chrome-specific bug.

Is DNS_PROBE_FINISHED_NXDOMAIN my fault or the website’s?

It can be either. If it happens on one device only, it’s local. If it happens on every device and network, the domain’s DNS setup is likely broken.

Does clearing my browser cache fix this?

Clearing the browser cache alone usually doesn’t help — you need to flush the DNS cache specifically (fix #1), which is a different, OS-level cache.

Google DNS or Cloudflare DNS — which is better?

Cloudflare’s 1.1.1.1 is typically faster and more privacy-focused. Google’s 8.8.8.8 has slightly broader compatibility testing. Both are free and reliable; either fixes most NXDOMAIN issues caused by a bad ISP DNS server.

Does this error happen on phones too?

Yes. On Android, forget and rejoin the Wi-Fi network or switch to mobile data. On iPhone, go to Settings → Wi-Fi → tap the (i) next to your network → Configure DNS → Manual → add 8.8.8.8 or 1.1.1.1.

What’s the difference between DNS_PROBE_FINISHED_NXDOMAIN and DNS_PROBE_FINISHED_NO_INTERNET?

NXDOMAIN means DNS resolution completed but found no record for the domain. NO_INTERNET means your device has no network connection at all, so DNS resolution couldn’t even start.

Can antivirus software cause this error?

Yes. Some antivirus tools filter or intercept DNS traffic and can misflag legitimate domains. Disabling it temporarily (fix #8) confirms whether it’s the cause.