sodcalculator

10 Tech How-To

DNS Probe Finished NXDOMAIN Error Fix

Guide 10-53352 · Updated · Step by step

The “DNS_PROBE_FINISHED_NXDOMAIN” error in Google Chrome means the browser cannot find the website’s address in the Domain Name System (DNS). The fix is usually to clear your DNS cache, change your DNS server to a public one like Google’s (8.8.8.8), or disable your VPN/proxy, and this article walks through each step in order.

What This Error Actually Means

When you type a web address, Chrome doesn’t connect directly to the site. It first asks a DNS server to translate the human-readable name (like example.com) into a numeric IP address (like 93.184.216.34). The NXDOMAIN part is a standard DNS response code that literally means “non-existent domain” — the server you queried has no record for that name. So the error is Chrome telling you: the DNS lookup failed, and the domain doesn’t exist as far as the DNS system is concerned.

This is different from other DNS errors like DNS_PROBE_FINISHED_NO_INTERNET (your device has no connection) or DNS_PROBE_FINISHED_BAD_CONFIG (your DNS settings are malformed). NXDOMAIN specifically points to a missing record. However, it’s often a false alarm — the site exists, but your local DNS cache, your router, or your ISP’s DNS server is serving stale or incorrect information.

Why It Happens: Common Causes

Before jumping to fixes, it helps to know what you’re dealing with. The most frequent culprits are:

  • Stale DNS cache: Your computer or router saved an old DNS response that no longer matches the current IP address of the site.
  • Incorrect DNS server settings: Your router or OS is pointed to a DNS server that is down, slow, or returning wrong results.
  • VPN or proxy interference: A VPN or a browser proxy can route DNS queries through a server that doesn’t have the right records.
  • Typo or dead link: The address itself is misspelled, or the site has genuinely been taken down.
  • Router firmware issues: Some routers have buggy DNS forwarding that fails intermittently.
  • Malware or browser extensions: Rare, but some extensions hijack DNS or proxy settings.

Fix 1: Clear Your DNS Cache (Fastest)

Your operating system stores DNS lookups locally to speed up browsing. If that cache holds an outdated or incorrect entry, you’ll get NXDOMAIN even though the site is live. Clearing it forces a fresh lookup.

  1. On Windows: Press Win + R, type cmd, press Enter. In the Command Prompt, type ipconfig /flushdns and press Enter. You should see “Successfully flushed the DNS Resolver Cache.”
  2. On macOS: Open Terminal (Finder > Applications > Utilities > Terminal). Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter. Enter your password if prompted.
  3. On Linux: The command varies by distribution. For systemd-resolved (most modern distros), use sudo systemd-resolve --flush-caches. For older setups, try sudo /etc/init.d/nscd restart or sudo service dnsmasq restart.
  4. Restart Chrome completely (close all windows, not just the tab) and try the site again.

If the error persists, move to the next fix.

Fix 2: Change Your DNS Server to a Public One

Your ISP’s DNS servers are often slow or occasionally return wrong results. Switching to a public, well-maintained DNS server resolves many NXDOMAIN errors. Two reliable options are Google Public DNS (8.8.8.8 and 8.8.4.4) and Cloudflare (1.1.1.1 and 1.0.0.1).

On Windows:

  1. Go to Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
  3. Select “Internet Protocol Version 4 (TCP/IPv4)” and click Properties.
  4. Choose “Use the following DNS server addresses” and enter 8.8.8.8 and 8.8.4.4 (or 1.1.1.1 and 1.0.0.1).
  5. Click OK, then close. Restart your browser.

On macOS:

  1. Go to System Settings > Network.
  2. Select your active connection and click Details.
  3. Go to the DNS tab, remove any existing servers, and click + to add 8.8.8.8 and 8.8.4.4.
  4. Click OK and restart Chrome.

If you prefer a GUI tool, you can also use a free utility like DNS Jumper (Windows) or simply edit the settings in your router’s admin page (usually at 192.168.1.1 or 192.168.0.1) — look for “DNS” under WAN or Internet settings.

Fix 3: Disable VPN, Proxy, and Browser Extensions

VPNs and proxy extensions often route DNS through their own servers, which can fail or block certain domains. Even if the VPN is connected, the DNS might be misconfigured.

  1. Turn off your VPN completely (not just disconnected — quit the app).
  2. In Chrome, go to Settings > System > Open your computer’s proxy settings. On Windows, ensure “Use a proxy server” is off. On macOS, go to Network > Advanced > Proxies and uncheck any active proxy protocols.
  3. Try Chrome in Incognito mode (Ctrl+Shift+N) — extensions are disabled by default there. If the site loads, an extension is the culprit. Go to chrome://extensions and disable them one by one.

Fix 4: Restart Your Router and Device

Sometimes the router’s internal DNS cache is the problem. A full power cycle clears it and re-establishes the connection to your ISP.

  1. Unplug the power cable from your router and modem (if separate).
  2. Wait 30 seconds.
  3. Plug the modem back in, wait for it to fully boot (all lights stable), then plug in the router.
  4. Once everything is back online, restart your computer and try the site again.

This also resets the network stack on your device, which can clear other transient glitches.

Fix 5: Check the Domain Itself

If none of the above work, the domain may genuinely be down or mistyped. Use an external tool like dns.google or dnschecker.org to query the domain’s DNS records. If the lookup returns NXDOMAIN from all servers, the domain doesn’t exist — check the spelling, or the site may have been shut down. If some servers return an IP but others don’t, it’s a propagation issue (common after a domain transfer or new site launch), and you can wait a few hours or temporarily use a different DNS server that has the correct record.

Frequently Asked Questions

Why does this error happen only in Chrome and not other browsers?

Chrome has its own built-in DNS cache (called the “async DNS resolver”) that is separate from the OS cache. If that internal cache gets corrupted or holds a stale entry, Chrome will show the error while Firefox or Edge (which use the OS resolver) work fine. The fix is to clear Chrome’s DNS cache by going to chrome://net-internals/#dns and clicking “Clear host cache.”

Will changing my DNS server affect my internet speed?

It can, but usually in a positive way. Public DNS servers like Google and Cloudflare are often faster than ISP servers because they have massive global infrastructure. You may see a slight improvement in the time it takes to resolve domain names, but your overall download speed won’t change — DNS only handles the “phone book” lookup, not the data transfer.

Is it safe to use public DNS servers?

Yes, using Google Public DNS or Cloudflare DNS is generally safe and even more private than your ISP’s DNS in some cases, because they don’t log your browsing history in the same way. However, you are trusting that company with your DNS queries, so if you are extremely privacy-conscious, you might prefer a service like Quad9 (9.9.9.9) which blocks malicious domains.

What does NXDOMAIN mean in plain English?

It stands for “Non-Existent Domain.” It’s a standard DNS response code that tells the client the requested domain name does not exist in the DNS system. In practice, it often means the DNS server you’re using doesn’t have a record for that domain, which could be because the domain is truly dead, or because the server’s data is outdated.

Can this error be caused by a virus?

In rare cases, yes. Some malware modifies your DNS settings or hosts file to redirect or block certain domains. If you’ve tried all the fixes and the error persists, scan your computer with a reputable antivirus program and check your hosts file (C:\Windows\System32\drivers\etc\hosts on Windows, /etc/hosts on Mac/Linux) for any unusual entries that don’t belong.

Why does the error appear on every site, not just one?

If you get NXDOMAIN on every site, the problem is almost certainly your DNS server or your network connection. Your DNS server might be down or misconfigured. Try switching to a public DNS as described in Fix 2, or restart your router. If that doesn’t help, contact your ISP — there may be a regional outage.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →