Quick Answer: DNS_PROBE_FINISHED_NXDOMAIN means Chrome can’t translate a website’s domain name into an IP address – either the site doesn’t exist, or your DNS server can’t resolve it. Switching to a public DNS server like Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) fixes it in most cases.
What Causes This Error
- Your router or ISP’s DNS server is down or misconfigured
- A typo in the URL, or a site that’s genuinely offline
- Stale DNS cache on your Chromebook
- A browser extension or parental control filter blocking the domain
- Corrupted network settings after a ChromeOS update
How to Fix It
Step 1: Double-check the URL
Typos are the most common cause. Confirm you typed the address correctly and try a well-known site like google.com to see if the problem is site-specific or affects everything.
Step 2: Clear your DNS cache
Open a new tab and go to chrome://net-internals/#dns, then click “Clear host cache.” This forces Chrome to re-resolve every domain from scratch.
Step 3: Switch to a public DNS server
Go to Settings > Network > Wi-Fi > (your network) > Network > Name servers, and switch from “Automatic” to “Google” (8.8.8.8, 8.8.4.4) or “Custom” and enter Cloudflare’s 1.1.1.1. This bypasses a broken or slow ISP DNS server entirely.
Step 4: Restart your router
Unplug it for 30 seconds. Many home routers act as the local DNS resolver, and a restart clears a stuck or corrupted lookup cache.
Step 5: Disable extensions and content filters
Ad blockers, VPNs, and parental control extensions sometimes intercept DNS requests and misfire on legitimate sites. Disable them one at a time from chrome://extensions to isolate the culprit.
Step 6: Flip airplane mode on and off
This resets the entire network stack on ChromeOS, including DNS resolution, without a full restart. Toggle it from the status area.
Still Not Fixed?
If the error follows you across every network and every DNS server you try, the site itself may genuinely be down or have expired its domain. Use a tool like a “down for everyone or just me” checker from another device to confirm. If it only happens on managed school or work Chromebooks, an administrator-level content filter is likely blocking the domain intentionally.
FAQ
Is DNS_PROBE_FINISHED_NXDOMAIN the same as “site can’t be reached”?
It’s a specific version of that broader error – it means Chrome successfully asked a DNS server and got back “this domain doesn’t exist,” rather than timing out.
Will changing DNS servers slow down my browsing?
No, public DNS providers like Google and Cloudflare are typically faster than default ISP DNS servers, not slower.
Does this affect all browsers, or just Chrome?
Since DNS resolution happens at the network level on ChromeOS, it typically affects every app that needs internet access, not just the Chrome browser.
