DNS_PROBE_FINISHED_NXDOMAIN fix that actually works

Quick answer for advanced users

Run ipconfig /flushdns in Command Prompt (Windows) or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal (macOS). Then try the site again. Still broken? Restart your router or switch to Google DNS (8.8.8.8 / 8.8.4.4).

What's actually happening here

This error shows up when Google Chrome (or any Chromium browser) can't resolve a domain name to an IP address. The NXDOMAIN part means the DNS server explicitly said "this domain doesn't exist." Happens to me maybe once a month, usually when a client's ISP DNS goes haywire or their local cache gets corrupted. Last week I had a call from a small law firm—half their staff couldn't access their own website. Turned out someone's kid installed a VPN on the office router. Classic.

The good news: it's almost never the website itself being down. It's your machine or network that's misconfigured. Let's fix it.

Fix steps (start here)

1. Flush your DNS cache. This clears out bad records your computer stored locally.
   Windows: Open Command Prompt as admin, type ipconfig /flushdns, hit Enter. You'll see "Successfully flushed the DNS Resolver Cache."
   macOS: Open Terminal, type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. It'll ask for your password. No output means it worked.
   Linux: sudo systemd-resolve --flush-caches (systemd-based) or sudo service nscd restart.
2. Restart your browser completely. Close all windows, quit Chrome entirely, then reopen. Don't just close the tab—kill the process. On Windows, check Task Manager for leftover Chrome processes.
3. Check if the site is actually live. Use a site like downforeveryoneorjustme.com. If it's down globally, it's not your problem. If it's just you, keep going.
4. Restart your router and modem. Unplug power from both, wait 30 seconds, plug modem back in first, then router after it's fully booted. This clears the router's internal DNS cache—which can hold stale records for hours.

Alternative fixes if the main ones fail

If flushing and restarting didn't work, you've got a deeper DNS issue. Here's what else to try.

Change your DNS server

Your ISP's DNS is often slow or flaky. Switch to a public one. I personally recommend Cloudflare (1.1.1.1) or Google (8.8.8.8, 8.8.4.4).
Windows: Go to Network & Internet settings → Change adapter options → right-click your connection → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Use the following DNS server addresses. Enter 1.1.1.1 and 1.0.0.1 (or 8.8.8.8 / 8.8.4.4).
macOS: System Preferences → Network → select your connection → Advanced → DNS tab → add the new servers. Remove any old ones.
Router: Log into your router's admin panel (usually 192.168.1.1 or 192.168.0.1) and change the DNS settings there. That way every device on the network gets the fix.

Disable IPv6 temporarily

Some ISPs have broken IPv6 DNS servers, and Windows tries IPv6 first. I've seen this on Comcast and Spectrum networks.
Windows: Network settings → Change adapter options → right-click connection → Properties → uncheck "Internet Protocol Version 6 (TCP/IPv6)" → OK. Reboot.
macOS: System Preferences → Network → Advanced → TCP/IP → Configure IPv6 → set to Link-local only.

Check for malware or proxy settings

Had a client last year whose computer had a rogue proxy enabled. Check Chrome settings: Settings → Advanced → System → Open proxy settings → make sure "Automatically detect settings" is on and no manual proxy is listed. Also run a Malwarebytes scan—some adware hijacks DNS.

Reset Winsock (Windows only)

If your network stack is corrupted, this can help. Open Command Prompt as admin and run netsh winsock reset, then reboot.

Prevention tip

Most people ignore DNS until it breaks. Don't be that person. Set your router to use Cloudflare or Google DNS permanently—it's faster and more reliable than your ISP's. Also, clear your browser cache and DNS cache once a month. Takes 10 seconds. For power users, consider using a browser like Brave or Firefox that has built-in DNS-over-HTTPS—it encrypts your DNS queries and bypasses your ISP's servers entirely.

One more thing: if you're working from a coffee shop or shared network, the router might block certain DNS requests. In that case, use a VPN or switch to your phone's hotspot to see if the error follows you. If it doesn't, the network's DNS is the culprit, not your machine.