Fix DNS_PROBE_FINISHED_NXDOMAIN (Chrome) – Quick Steps

You're working along, type a URL into Chrome, hit Enter, and instead of the page you get that gray screen with DNS_PROBE_FINISHED_NXDOMAIN. It's happened to me a hundred times in the last decade, usually right when I'm in the middle of something. The trigger is almost always one of three things: a stale DNS cache, a flaky DNS server provided by your ISP, or a typo in the hosts file that you forgot about. Sometimes it's a domain that genuinely doesn't exist, but you wouldn't be here if that were the case.

What's Actually Happening?

This error means Chrome tried to resolve the domain name to an IP address, and the DNS server came back with a big fat "doesn't exist." The NXDOMAIN part is literally the DNS protocol's way of saying "No Such Domain." That can happen because the domain is dead, but more often it's because your computer is holding onto an old negative cache entry, or your DNS server is misbehaving.

Think of DNS like a phonebook. If the phonebook says "no listing," your browser can't call. So we need to clear the bad entry and make sure the phonebook is actually the right one.

Step-by-Step Fix

Here's the order I use. It goes from quick and dirty to more invasive. Start at step 1, and only move down if the problem persists.

Flush the DNS cache. Open Command Prompt as Administrator (right-click Start, select "Command Prompt (Admin)" or "Terminal (Admin)"). Then run:
```
ipconfig /flushdns
```
You'll see "Successfully flushed the DNS Resolver Cache." Now try the site again. This clears the local cache that might be holding the stale NXDOMAIN response.
Check the hosts file. Sometimes a leftover entry in the hosts file points a domain to a dead IP. Open Notepad as Administrator and load C:\Windows\System32\drivers\etc\hosts. Look for any line that mentions the domain you're trying to reach. If you see one, put a # at the start of that line to comment it out, then save and retry. I've seen this bite people who installed software that tweaked the hosts file and forgot to remove it.
Switch DNS servers. Your ISP's DNS is often the culprit. It might be down or just slow to update. I've been using Google's public DNS for years, and it's solid. Hit Win + R, type ncpa.cpl, hit Enter. Right-click your active connection (Ethernet or Wi-Fi), select Properties. Highlight "Internet Protocol Version 4 (TCP/IPv4)" and click Properties. Select "Use the following DNS server addresses" and set:
```
Preferred DNS server: 8.8.8.8
Alternate DNS server: 8.8.4.4
```
Click OK, then close everything. No need to reboot, but you might want to flush DNS again.
Clear Chrome's internal cache. Chrome has its own DNS cache that can go stale. Type chrome://net-internals/#dns in the address bar and hit Enter. Click the "Clear host cache" button. While you're there, go to chrome://net-internals/#sockets and click "Flush socket pools." That forces Chrome to drop any bad connections it's holding onto.
Try a different browser or device. If Firefox or your phone loads the site fine, then the problem is local to Chrome or your PC. If it fails on every device on your network, then it's your router or the DNS server you're pointing to. That narrows things down fast.

If It Still Fails

Okay, you've done all that and you're still staring at the error. Don't panic. Here's what to check next.

Verify the domain actually exists. Use nslookup or an online tool like MXToolbox. Open Command Prompt and type:
```
nslookup example.com 8.8.8.8
```
Replace example.com with the real domain. If it returns an IP, the domain is alive. If it says "Non-existent domain," then the site might really be gone, or the domain's DNS is messed up on their end. Not your problem.
Check your VPN or proxy settings. A VPN can hijack DNS resolution, and sometimes it breaks. Disconnect from any VPN and try again. Also check Windows proxy settings: Win + R, inetcpl.cpl, go to Connections tab, click LAN settings. Make sure "Automatically detect settings" is checked and the proxy server box is empty unless you know you need it.
Run Windows network troubleshooter. It's not my go-to, but sometimes it catches something dumb like a disabled adapter. Right-click the network icon in the system tray, select "Troubleshoot problems," and let it run.
Finally, reboot your router. I hate to say it, but a quick power cycle fixes a surprising number of DNS issues. Unplug it, wait 30 seconds, plug it back in. This resets the router's own DNS cache and DHCP leases. Do this if nothing else worked.

If you've gone through all that and the error only appears on one specific site, then it's almost certainly a problem with that site's DNS records. You can't fix that from your end. Wait it out or contact them. But for the 90% of cases where it's a local cache or DNS config issue, the steps above will get you back online.