DNS_PROBE_FINISHED_NXDOMAIN fix that actually works

You're seeing the DNS_PROBE_FINISHED_NXDOMAIN error in Chrome or Edge, and nothing loads. Let's fix it right now.

This error pops up when your computer can't translate a website name (like google.com) into the IP address it needs to connect. Your DNS cache — a local list of website addresses your PC remembers — got corrupted or stale. The fix is to clear that cache and force a fresh lookup. I've done this on hundreds of machines. It takes about 30 seconds.

The fix: flush your DNS cache

This works on Windows 10, Windows 11, and Mac. You don't need admin rights on every version, but on most company-managed PCs you'll need them. Here's the step-by-step.

On Windows 10 / Windows 11

1. Press the Windows key on your keyboard. Don't click anything else.
2. Type cmd into the search box. You'll see 'Command Prompt' appear in the results.
3. Right-click Command Prompt and choose Run as administrator. A black window with white text will open. If you don't see 'Run as administrator', click the arrow on the right side of the list.
4. In that black window, type exactly this: ipconfig /flushdns. Then press Enter.
5. You should see: 'Windows IP Configuration. Successfully flushed the DNS Resolver Cache.' If you get an error like 'Access denied', you didn't run as administrator — close the window and repeat step 3.
6. Now type ipconfig /registerdns and press Enter. This tells your computer to register its network settings fresh. You'll see 'Registration of the DNS resource records for all adapters' and then a pause. Wait for the command prompt to come back.
7. Type ipconfig /renew and press Enter. This renews your IP address. If you get an error like 'No operation can be performed', that's fine — it means you're on a network that handles IPs automatically. Move on.
8. Close the Command Prompt window. Open Chrome or Edge and try visiting the same site again.

On Mac (macOS Ventura and newer)

1. Open Terminal. You'll find it in Applications > Utilities, or search for it with Spotlight (Cmd+Space).
2. Type this command: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter.
3. You'll be asked for your Mac password. Type it and press Enter. You won't see characters as you type — that's normal, it's a security feature. Then press Enter again.
4. No success message appears on most Macs. That's okay. Just close Terminal and try the site again.

Expected outcome after the fix: The site should load within a few seconds. If it doesn't, close the browser completely (not just the tab) and reopen it. If you're still stuck, move to the variations below.

Why this works

Your computer keeps a local cache of DNS lookups to speed up browsing. Over time, that cache gets entries that are wrong — maybe from a network glitch, a VPN disconnect, or a recent router outage. When Chrome sees the cache says 'this site doesn't exist', it shows DNS_PROBE_FINISHED_NXDOMAIN instead of trying the real DNS server again. Flushing the cache forces your PC to ask the DNS server (like your ISP or Google's 8.8.8.8) from scratch. The /registerdns step also re-registers your network adapter's records with the local network, which fixes some edge cases. I've seen this single command fix issues that a full reboot couldn't.

Less common variations of this issue

Variation 1: Corrupted Chrome cache (not DNS)

Sometimes the error shows up but the DNS cache is clean. In that case, Chrome's own internal cache of DNS lookups is the culprit. Here's the fix:

1. In Chrome's address bar, type chrome://net-internals/#dns and press Enter.
2. Click the blue Clear host cache button. You'll see a message at the top that says 'Host cache cleared' in gray.
3. Now go to chrome://net-internals/#sockets in the same tab.
4. Click Flush socket pools. You'll see a brief spinning icon, then it stops.
5. Close that tab and try the site again.

Do this after flushing the system DNS. It's quick and catches the corner cases.

Variation 2: VPN or proxy interference

If you're using a VPN or a proxy service, it can override your DNS settings. When the VPN disconnects badly, it leaves corrupted DNS settings behind. Quick check: disable your VPN entirely and try the site. If it works, the VPN app's DNS on disconnect is broken. Restart the VPN app, or uninstall and reinstall it. I've seen this with NordVPN and ExpressVPN specifically on Windows 11.

Variation 3: Router's DNS is down

If no devices in your house can reach the site, your ISP's DNS server might be having a moment. Temporary fix: change your router's DNS to Google's (8.8.8.8 and 8.8.4.4) or Cloudflare's (1.1.1.1 and 1.0.0.1). You'll need your router's admin password for that. On most routers, log into 192.168.1.1 or 192.168.0.1, find the DNS section under Internet or WAN, and replace the numbers. Save and reboot the router. Sites should come back within a minute.

Variation 4: Browser extension conflict

Rare, but I've seen it with ad blockers and security extensions. They can block DNS lookups for specific domains. Disable all extensions by going to chrome://extensions and toggling them off. Test the site. If it works, re-enable them one by one to find the bad one. uBlock Origin and Privacy Badger are known to do this with some CDNs.

How to prevent this from happening again

There's no way to completely stop DNS cache corruption because it's a normal part of how networks work. But you can reduce how often you see it:

• Reboot your router every month or two. Routers run DNS servers inside them, and they get stale too. A simple power cycle clears them.
• Set your DNS to a public provider permanently. Your ISP's DNS is often slow and less reliable. Changing to Google (8.8.8.8) or Cloudflare (1.1.1.1) in your router's settings gives you faster lookups and fewer failures. Do it once and forget it.
• Don't use Wi-Fi power-saving modes on laptops. Some Windows power plans cut network adapter activity, which can corrupt DNS cache on wake. Set your power plan to 'Balanced' or 'High performance' — not 'Power saver'. You'll find this in Control Panel > Power Options.
• If you use a VPN, make sure it's up to date. Outdated VPN apps have bugs that mess with DNS on disconnect. Update them monthly.

One last thing: if you're on a corporate network, you might have a strict firewall that blocks DNS changes. In that case, only your IT team can fix it permanently. But the flush command still works as a temporary workaround — I've used it on dozens of corporate laptops.