When Chrome throws DNS_PROBE_FINISHED_NXDOMAIN, the page never loads. I’ve seen it pop up on fresh installs, after VPN churn, and even on hardened corporate laptops. The error means the resolver could not find an address for the host name. It’s not a Chrome bug; it’s a DNS chain that broke somewhere.
Below is the checklist I use for every ticket. Pick the steps that match your environment. Run them in order; stop when the page finally renders.
1. Flush the local resolver cache
Windows, macOS, and Linux keep a small cache. A stale entry will keep Chrome stuck.
# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
# Linux (systemd‑resolved)
sudo systemd-resolve --flush-caches
A quick ping after the flush should return unknown host if the problem persists.
2. Restart the network stack
Sometimes the NIC driver holds onto a bad DNS server address.
- Windows:
netsh int ip resetthen reboot. - macOS: Turn Wi‑Fi off, wait five seconds, turn it back on.
- Linux:
sudo systemctl restart NetworkManager.
3. Verify the DNS server you’re using
If your ISP’s DNS is down, every request fails. I swap to Google’s or Cloudflare’s resolvers in a pinch.
# Windows
netsh interface ip set dns "Wi‑Fi" static 8.8.8.8 primary
netsh interface ip add dns "Wi‑Fi" 8.8.4.4 index=2
# macOS / Linux (edit /etc/resolv.conf)
nameserver 1.1.1.1
nameserver 1.0.0.1
After the change, run nslookup example.com. If you get an answer, the DNS path is alive.
4. Inspect the hosts file
A rogue entry can shadow a legitimate domain.
- Windows:
C:\Windows\System32\drivers\etc\hosts - macOS / Linux:
/etc/hosts
Look for lines that map the target domain to 127.0.0.1 or any non‑routable address. Comment them out and save.
5. Disable Chrome extensions temporarily
Some ad‑blockers or privacy extensions rewrite DNS queries. Open Chrome in incognito mode or launch with --disable-extensions:
chrome.exe --disable-extensions
If the page loads, isolate the culprit by re‑enabling extensions one at a time.
6. Clear Chrome’s internal network data
Chrome stores its own DNS cache separate from the OS.
- Open
chrome://net-internals/#dns. - Click Clear host cache.
- Then go to
chrome://net-internals/#socketsand press Flush socket pools.
7. Check the router’s DNS configuration
A misconfigured router will hand out bad DNS servers to every client. Log into the admin UI, locate the DNS settings, and set them to known public resolvers (8.8.8.8, 1.1.1.1). Reboot the router.
8. Test with a different browser or device
If Firefox or Edge can reach the site, the issue is Chrome‑specific. If all browsers fail, the problem sits upstream—likely the ISP or corporate DNS.
9. Run a full DNS lookup
A proper lookup will show you where the resolution chain breaks. Use a tool like dig or an online service. This step also reminds you to check your DNS records for typos or missing A/AAAA entries.
10. When everything else fails
- Reset Chrome to default settings (
chrome://settings/reset). - Reinstall Chrome from the official installer.
- Contact the network administrator if you’re on a managed subnet; there may be DNS policies blocking the domain.
Bottom line: The error is a symptom, not a cause. Follow the list, isolate the layer that fails, and you’ll have Chrome loading again in minutes.
Stay Ahead on Protocol Changes
Get our authoritative engineering deep dives on Gmail/Yahoo bulk sender rules, post-quantum TLS, and DNS standards directly in your inbox. No marketing fluff.
Maximum 1 email per week · Unsubscribe with 1 click
Related tools
View all toolsDNSSEC Validator
Free DNSSEC validator. Verify the cryptographic chain of trust from ICANN root down to zone apex. Inspect DS records, DNSKEY public keys, and RRSIG validity.
DNS Time Machine
Free DNS Time Machine. Track DNS record changes with git-style visual diffs (+/-) and export standard RFC 1035 BIND zone files for 1-click disaster recovery.
DNS Propagation
Free global DNS propagation checker. Test A, AAAA, CNAME, MX, and TXT records across 12 worldwide edge locations with expected value matching and Geo-DNS detection.