ERR_NAME_NOT_RESOLVED means Chrome could not turn a website name into an address it can connect to. It is another DNS lookup failure, similar to DNS_PROBE_FINISHED_NXDOMAIN, and it often appears on Android Chrome, embedded browser windows, and sometimes desktop Chrome.
Does this affect you?
Use this for Chrome, Edge, and Chromium browsers on Windows, Mac, Chromebook, or Android when a page fails with ERR_NAME_NOT_RESOLVED. If desktop Chrome instead shows DNS_PROBE_FINISHED_NXDOMAIN, the same DNS-focused fixes apply.
Check the basics first
Most name-resolution errors come from a typo, connection issue, or router glitch.
- Double-check the web address for a wrong letter or incorrect ending.
- Try a known website such as google.com. If that fails too, focus on the connection.
- Confirm Wi-Fi, cellular, or Ethernet is connected.
- Restart the router by unplugging it for one full minute, then waiting two or three minutes after plugging it back in.
- Hard reload the page with Ctrl+Shift+R on desktop or Cmd+Shift+R on Mac. On Android, close and reopen the tab or restart Chrome.
Flush your DNS cache
Clearing stale local DNS data can restore the lookup.
- On Windows, open Command Prompt as administrator and run ipconfig /flushdns.
- On Mac, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
- On Android, restart the phone, or use chrome://net-internals/#dns and Clear host cache if that page is available on your build.
- In desktop Chrome, open chrome://net-internals/#dns and click Clear host cache.
- Close and reopen Chrome, then test the site.
Switch to a different DNS server
If your current DNS provider is failing, public DNS can fix the error quickly.
- On Windows, edit DNS server assignment for your active Wi-Fi or Ethernet connection and set IPv4 DNS to 8.8.8.8 and 8.8.4.4.
- On Mac, open Wi-Fi details, choose DNS, and add 8.8.8.8 and 1.1.1.1.
- On Android, open network settings for your Wi-Fi and use Private DNS with dns.google, or set static DNS on older Android versions.
- Restart Chrome and try again.
More control
One site may have broken DNS
If every other site loads, the website itself may have a DNS misconfiguration. Check from another connection or wait for the site owner to fix it.
Test VPNs and security tools
VPN apps and security software can route DNS through their own servers. Disable them temporarily for testing, then re-enable protection after you identify the cause.
Check router-level DNS
If several devices on the same network show the error, log into the router and review DNS settings. Fixing DNS on the router helps every device at once.
Use network resets only after easier fixes
On Windows, netsh winsock reset and netsh int ip reset can repair deeper network issues. On Android, Reset Wi-Fi, mobile and Bluetooth clears network configuration. Both can remove custom network settings, so use them late in the process.
Sources
- Google Chrome Help – Fix connection errors (2025)
- Chromium Project – Net error list documentation (2025)
- Cloudflare Learning Center – What is DNS? (2025)