How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome: 7 Proven Fixes

You're on a deadline, you type a URL into Chrome, and instead of the site you expect, you get a message: DNS_PROBE_FINISHED_NXDOMAIN. Your internet connection is fine. Other sites load. But this one - or sometimes all of them - refuses to appear. This error is one of the most common DNS failures, and it's fixable. In this guide, you'll learn what it means and seven practical ways to resolve it, from simple checks to deeper network resets.

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

DNS stands for Domain Name System. It translates a human-readable domain like example.com into an IP address that your computer can connect to. NXDOMAIN is short for "nonexistent domain." Chrome is telling you that the domain you requested does not exist according to the DNS server you're using.

But "does not exist" doesn't always mean you typed the wrong address. Often, the DNS server itself is out of date, your local DNS cache is corrupted, or a VPN or proxy is sending you down a broken path. That's why these fixes work even when the site is perfectly alive.

Fix 1: Check the URL and Reload

Yes, it's the obvious one, but it's also the most common cause. A single typo - an extra dot, a misspelled word, a wrong top-level domain like .com instead of .net - can trigger NXDOMAIN. Before you change any settings, verify:

• The spelling of the domain name.
• The top-level domain (.com,.org,.net, etc.).
• You're not missing a subdomain like www. - some sites require it.
• There's no extra space in the address.

If the URL is correct, try a hard reload: press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac). If the error disappears, you're done. If not, move to Fix 2.

Fix 2: Flush Your DNS Cache

Your computer stores DNS lookups locally to speed up browsing. If this cache becomes stale or corrupted, it can return a "nonexistent domain" result. Clearing it forces your system to ask a DNS server from scratch.

Windows:

1. Press Win + R, type cmd, and hit Enter.
2. In the Command Prompt, type ipconfig /flushdns and press Enter.
3. You'll see "Successfully flushed the DNS Resolver Cache."

macOS:

1. Open Terminal.
2. Run the appropriate command for your version:

• macOS Catalina and later: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Older versions: sudo killall -HUP mDNSResponder

After flushing, restart Chrome and reload the page.

Fix 3: Switch to a Public DNS Server

Your internet service provider's DNS is often the weak link. It may be slow, outdated, or occasionally unreliable. Switching to a well-known public DNS server like Google Public DNS or Cloudflare's 1.1.1.1 can resolve many DNS_PROBE errors instantly.

To change it on Windows:

1. Open Control Panel > Network and Sharing Center.
2. Click your active connection (Ethernet or Wi-Fi), then Properties.
3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
4. Choose "Use the following DNS server addresses" and enter:

Preferred: 8.8.8.8
Alternate: 8.8.4.4 (or 1.1.1.1 and 1.0.0.1 for Cloudflare)

1. Click OK and close all windows.

On macOS:

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

Then flush your DNS again using Fix 2.

Fix 4: Restart Your Router and Modem

Your router has its own DNS cache. Even if your computer is configured correctly, a corrupt router cache can return NXDOMAIN for every request. Resetting your network hardware is safe and often clears the problem.

1. Unplug the power from your modem and router.
2. Wait at least 30 seconds.
3. Plug the modem back in, wait for all lights to connect, then plug in the router.
4. When the network is fully back, restart Chrome and try the site again.

If you don't want to wait, you can also log into your router's admin panel and look for a "Reboot" option.

Fix 5: Turn Off VPN, Proxy, and Browser Extensions

VPNs and proxy extensions route your traffic through other servers. If those servers' DNS is misconfigured, you'll see DNS_PROBE_FINISHED_NXDOMAIN. The same goes for certain Chrome extensions that intercept network requests.

Try this:

1. Turn off your VPN or disconnect from it.
2. Disable any proxy in Chrome: Go to Settings > System > Open your computer's proxy settings and ensure "Use a proxy server" is off (or set to automatic).
3. Open Chrome's extension manager (chrome://extensions) and disable any extensions related to VPN, ad-blocking, or security.

If the page loads after disabling an extension, that extension is the culprit. Re-enable them one by one to find the exact one causing the issue.

Fix 6: Clear Chrome's Host Cache and Network Data

Chrome keeps its own DNS cache and a list of open sockets. A corrupted entry there can cause NXDOMAIN even when your system DNS is fine. To clear it:

1. Open a new tab and go to chrome://net-internals/#dns.
2. Click the Clear host cache button.
3. Go to chrome://net-internals/#sockets and click Flush socket pools.
4. Close and reopen Chrome.

You can also clear regular Chrome data: Go to Settings > Privacy and security > Clear browsing data. Choose "Cached images and files" and "Cookies and other site data," then click Clear data. This logs you out of some sites, but it's a common fix for network errors.

Fix 7: Check for Malware or Browser Hijackers

While less common, some malware can alter your DNS settings at the system or router level. If none of the above fixes work, run a malware scan. Windows has Microsoft Defender built in:

1. Open Windows Security.
2. Go to Virus & threat protection.
3. Click Scan options and select Full scan.
4. Let it finish and act on anything found.

On macOS, you can use the built-in malware removal tool (check System Settings > Privacy & Security > Security) or a trusted third-party scanner. Also, check your device's proxy settings for anything unusual - a hijacker often appends a strange server address.

What If the Error Persists on One Site?

If you can load other sites but not one specific domain, the problem may be on the site's side. Use a site checker like downforeveryoneorjustme.com to see if the site is down for everyone. If it's down, you just need to wait. If it's up, the domain might be newly registered or experiencing DNS propagation delays - especially after a server move or name server change. In that case, waiting a few hours usually fixes it.

Frequently Asked Questions

Is DNS_PROBE_FINISHED_NXDOMAIN a virus?

No, it's not a virus. It means Chrome can't find the IP address for the domain. However, a browser hijacker or malware on your system could cause a persistent DNS error, which is why we included a malware scan in Fix 7.

Why does DNS_PROBE_FINISHED_NXDOMAIN happen on only one device?

If the error appears on one device but not others, the problem is likely in that device's local DNS cache or network settings. Try flushing the DNS cache, changing DNS servers on that device, or turning off any VPN/proxy running there.

How do I clear DNS cache on my router?

Most routers don't have a direct "clear DNS cache" button. Instead, reboot the router as described in Fix 4. That resets its internal memory, including any cached DNS entries.

Can changing DNS servers make my internet faster?

It can, in some cases. Public DNS servers like 1.1.1.1 or 8.8.8.8 are often faster and more reliable than ISP default servers, but the main benefit here is fixing resolution errors like NXDOMAIN.

Key Takeaways

• DNS_PROBE_FINISHED_NXDOMAIN means Chrome couldn't find the domain's IP address - it doesn't always mean the site is offline.
• Quick fixes: check the URL, flush your system DNS cache, and restart your router.
• Using a public DNS server (like 8.8.8.8 or 1.1.1.1) solves many persistent cases.
• VPNs, proxies, and browser extensions can also cause this error - disable them to test.
• If the problem only affects one site, the site itself may be down or still propagating its DNS.