DNS_PROBE_FINISHED_NXDOMAIN – What Actually Breaks and How to Fix

Corrupt DNS Cache (The 80% Case)

What's actually happening here is Chrome sends a DNS query through your OS resolver, and the cached result says 'this domain doesn't exist' — even though it does. Your DNS cache got poisoned or stale. This happens a lot after you switch Wi-Fi networks, use a VPN, or install software that messes with network settings (looking at you, Cisco AnyConnect).

How to flush the DNS cache

Skip the router restart for now. Do this on your machine:

• Windows 10/11: Open Command Prompt as admin, run ipconfig /flushdns. You'll see 'Successfully flushed the DNS Resolver Cache' if it works. Then run ipconfig /registerdns and ipconfig /release && ipconfig /renew to refresh your IP lease too — I've seen the DNS cache survive without those extra steps.
• macOS Ventura/Sonoma: Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. The mDNSResponder restart is the actual flush — dscacheutil alone doesn't cut it on newer macOS versions.
• Linux (systemd-resolved): sudo systemd-resolve --flush-caches or sudo resolvectl flush-caches depending on your distro. On Ubuntu 22.04+, resolvectl is the way.

After flushing, close and reopen the browser tab. Don't just refresh — Chrome caches DNS per tab session. Kill it with Ctrl+W and reopen.

If the error's gone, you're done. If not, the issue's deeper.

Bad DNS Server Configuration (Router or OS Level)

Your ISP's DNS servers might be flaky, or you've got a stale static DNS entry. The reason step 1 didn't help is because every new request still hits the same broken server.

Switch to Google DNS (or Cloudflare)

I'm not saying Google DNS is perfect — but it's fast and rarely goes down. Here's the setup:

• Windows: Go to Network & Internet > Change adapter options. Right-click your active adapter, Properties, select Internet Protocol Version 4 (TCP/IPv4). Check 'Use the following DNS server addresses'. Set Preferred to 8.8.8.8, Alternate to 8.8.4.4. Click OK. Then ipconfig /flushdns again.
• macOS: System Settings > Network > your connection > Details > DNS. Remove any existing entries, add 8.8.8.8 and 8.8.4.4. Click OK, then flush DNS.
• Router level: Log into your router (usually 192.168.1.1 or 192.168.0.1), find WAN or Internet settings, locate DNS fields, swap to 8.8.8.8 and 8.8.4.4. Save and reboot the router. This fixes it for every device on your network at once.

I prefer Cloudflare's 1.1.1.1 and 1.0.0.1 for privacy, but Google's more widely compatible. If you've got a Pi-hole or AdGuard Home, check its logs — your internal DNS might be blocking legitimate domains.

Chrome's Built-in DNS Over HTTPS (DoH) Conflict

Chrome 83+ has a hidden setting that sends DNS queries directly to Google's servers over HTTPS. Sounds great — until it conflicts with your system DNS or corporate proxy. The error then becomes intermittent: some sites work, others get NXDOMAIN.

Disable Chrome's DNS-over-HTTPS

1. In Chrome's address bar, type chrome://net-internals/#dns and press Enter.
2. Click 'Clear host cache' — this flushes Chrome's internal DNS, not the OS cache.
3. Then go to chrome://flags/#enable-doh in the address bar.
4. Uncheck 'Enabled' (set to 'Disabled').
5. Restart Chrome completely (not just a restart — close all Chrome processes via Task Manager).

If you're on a corporate network, DoH might be blocked anyway. Disabling it forces Chrome back to your system's DNS, which is what you want.

Quick fix for Android phones

Go to Settings > Network & Internet > Private DNS. If it's set to 'Automatic', change to 'Off' or 'Hostname' (e.g., dns.google). The 'Automatic' mode on Android sometimes picks a broken private DNS provider.

Quick-Reference Summary Table

Try them in that order. The DNS cache flush works 80% of the time. If you're still stuck after all three, you've got a firewall rule blocking UDP port 53, or your ISP is intercepting DNS and injecting NXDOMAIN for certain sites. Test with nslookup google.com in the terminal — if it returns an IP, the problem is specific to your browser profile or an extension.