DNS_PROBE_FINISHED_NXDOMAIN: Why It Happens & How to Fix It

1. Corrupted DNS Cache (Most Common Fix)

I saw this error a lot on my blog—especially after people switched Wi-Fi networks or moved their laptop between home and office. The cached DNS records got stale, and Chrome just couldn't find the server. The fix is simple: flush the DNS cache.

On Windows 10 or 11, open Command Prompt as Administrator (right-click Start, choose Command Prompt (Admin) or Windows Terminal (Admin)). Run this command:

ipconfig /flushdns

You'll see a message like Successfully flushed the DNS Resolver Cache. That's it. Close the terminal and refresh the page. I've fixed this error in under 30 seconds doing this.

On Mac (macOS Ventura/Sonoma), open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Type your admin password when prompted. No confirmation message appears, so just trust it worked. Then reload the page.

On Linux (systemd-resolved), use:

sudo systemd-resolve --flush-caches

If you're using Chrome's built-in DNS service, also clear Chrome's internal cache: go to chrome://net-internals/#dns and click Clear host cache. Won't hurt, might help.

2. ISP DNS Server Issues (Second Most Common)

Your ISP's default DNS servers can be slow, unreliable, or just plain broken. I've seen Comcast, Spectrum, and BT users hit this error during peak hours. The fix is to switch to a public DNS server like Google DNS or Cloudflare DNS.

On Windows, go to Network & Internet settings, click Change adapter options, right-click your active connection (Wi-Fi or Ethernet), select Properties, double-click Internet Protocol Version 4 (TCP/IPv4), and choose Use the following DNS server addresses. Enter:

Preferred: 8.8.8.8
Alternate: 8.8.4.4

Or for Cloudflare (faster in some regions):

Preferred: 1.1.1.1
Alternate: 1.0.0.1

On Mac, go to System Settings > Network, select your Wi-Fi, click Details > DNS tab, hit the + button, and add those same IPs. Drag them to the top of the list. Then flush cache again (see fix #1) before testing.

On your router (if you want to fix it for every device), log into your router's admin page—usually 192.168.1.1 or 192.168.0.1—find DNS settings under WAN or Internet, and replace the ISP's addresses with Google DNS. Save and reboot the router. This takes about 5 minutes but saves you from fixing each device individually.

I prefer Cloudflare DNS (1.1.1.1) for privacy—they don't log your browsing history. Google DNS logs anonymized data but works great for reliability.

3. Router or Modem Glitch (Less Common but Worth Checking)

Sometimes the router itself gets confused. I've seen this after a power outage or when a router has been running for months without a reboot. The DNS proxy inside the router stops responding correctly, and every device on your network hits this error.

Try a full power cycle: unplug both the modem and the router from power. Wait 60 seconds (seriously—set a timer). Plug the modem back in and wait for all lights to stabilize (usually 2 minutes). Then plug in the router. Wait another 2 minutes, then try loading the site.

If that doesn't work, log into your router and double-check that DHCP is handing out valid DNS servers. Go to LAN settings, find DHCP Server, and make sure the DNS option is set to something like 8.8.8.8 (not blank or pointing to a dead server). Some routers, especially older Netgear models, default to their own IP as the DNS server, which can fail if the router's DNS proxy is buggy. I've seen this on Netgear R7000 models running old firmware. Updating the router's firmware might also help—check the manufacturer's support page.

One more thing: if you're using a VPN, disconnect it temporarily. Sometimes the VPN's DNS tunnel can cause NXDOMAIN errors—especially with split-tunneling turned on. If the error goes away after disconnecting the VPN, you know where the problem lies.

Quick-Reference Summary Table