Quick answer: ERR_NAME_RESOLUTION_FAILED means Chrome’s built-in DNS resolver (often using DNS-over-HTTPS) failed to look up a domain, separate from the more common ERR_NAME_NOT_RESOLVED. Switching your DNS settings or temporarily disabling secure DNS usually resolves it.
What ERR_NAME_RESOLUTION_FAILED Means
Before your Chromebook can load any website, it has to translate a domain name (like chromebookfixes.com) into an IP address through DNS. This specific error tends to show up when Chrome’s async DNS resolver — the internal system that also handles secure DNS-over-HTTPS lookups — can’t complete that translation, distinct from a standard operating-system-level DNS failure.
Common Causes
- A misconfigured or unreachable custom DNS server in your Chromebook’s network settings.
- Secure DNS (DNS-over-HTTPS) pointed at a provider that’s temporarily down or blocked on your network.
- A managed school or work network that blocks the DNS-over-HTTPS provider Chrome is trying to use.
- A temporary Wi-Fi or router issue affecting DNS traffic specifically.
How to Fix ERR_NAME_RESOLUTION_FAILED
- Reload the page — this is often a brief resolver hiccup that clears on its own.
- Check your secure DNS settings. Go to Settings > Privacy and security > Security, and either switch the “Use secure DNS” provider or temporarily set it to “With your current service provider” to test.
- Change your DNS server manually to a reliable public option like 8.8.8.8 or 1.1.1.1 — see our guide to changing DNS settings on a Chromebook.
- Reset network settings if the problem is affecting every site consistently — see our network reset guide.
- Try a different network (mobile hotspot) to check whether the issue is specific to your current Wi-Fi or router.
Still Not Fixed?
If you’re on a school or work Chromebook and this only happens on the managed network, ask your IT administrator — some networks block the DNS-over-HTTPS providers Chrome defaults to, which needs to be allowlisted on their end, not fixed on your device.
FAQ
Is this the same as DNS_PROBE_FINISHED_NXDOMAIN?
No. DNS_PROBE_FINISHED_NXDOMAIN means the domain simply doesn’t exist. ERR_NAME_RESOLUTION_FAILED means the lookup itself failed to complete, often due to secure DNS configuration rather than a nonexistent domain.
Should I turn off secure DNS permanently?
Not necessarily — it’s a genuine privacy improvement. Only switch it if you’re consistently hitting this error and a different provider or your ISP’s default resolves it.
