ERR_NAME_NOT_RESOLVED is a DNS lookup failure error that appears in Chrome and Chromium-based browsers when the browser cannot translate a domain name into an IP address. This guide explains every cause and walks you through each fix in order of likelihood.
Every website visit starts with a DNS lookup — your device asks a DNS resolver "what is the IP address for this domain?" If that query fails, the browser shows ERR_NAME_NOT_RESOLVED. The failure can originate from several places:
| Cause | Who is affected | Likely fix |
|---|---|---|
| Stale DNS cache on your device | One device only | Flush DNS cache |
| ISP DNS resolver is slow or down | All devices on same network | Switch to Google/Cloudflare DNS |
| Domain has expired or DNS records deleted | Everyone worldwide | Check domain registration |
| Hosts file override | One device only | Edit hosts file |
| VPN or proxy routing DNS incorrectly | One device only | Disconnect VPN/proxy |
| Corrupt browser DNS cache | One browser only | Clear browser cache / chrome://net-internals |
| Firewall blocking port 53 (DNS) | All devices on network | Check firewall rules |
Before working through each fix, answer these questions to narrow down the cause:
Your operating system caches DNS responses to speed up browsing. If a cached entry is stale or corrupt, flushing it forces a fresh lookup.
ipconfig /flushdns
ipconfig /release
ipconfig /renewsudo dscacheutil -flushcache
sudo killall -HUP mDNSRespondersudo systemd-resolve --flush-caches
sudo systemd-resolve --statisticsYour ISP's DNS resolver may be slow, overloaded, or blocking certain domains. Switching to a public resolver is one of the most effective fixes.
| Provider | Primary DNS | Secondary DNS |
|---|---|---|
| 8.8.8.8 | 8.8.4.4 | |
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| OpenDNS | 208.67.222.222 | 208.67.220.220 |
Change DNS in: Windows → Network Adapter Settings → IPv4 Properties | macOS → System Settings → Network → DNS | Router admin panel → WAN DNS settings (affects all devices)
A corrupted TCP/IP stack or Winsock catalogue can cause DNS resolution failures even when the DNS server itself is reachable.
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
Restart-Computersudo ifconfig en0 down
sudo ifconfig en0 upThe hosts file can override DNS for specific domains. If a domain is mapped to an incorrect IP (or 0.0.0.0 to block it), the browser will fail to connect.
C:\Windows\System32\drivers\etc\hostssudo nano /etc/hostsChrome maintains its own internal DNS cache separate from the OS cache. Clear it via the hidden diagnostics page:
chrome://net-internals/#dnsClick Clear host cache, then navigate to chrome://net-internals/#sockets and click Flush socket pools.
VPNs and proxy servers route DNS queries through their own resolvers. If the VPN's DNS server is unreachable or misconfigured, every DNS lookup fails. Temporarily disable your VPN or proxy and retry the URL. If it loads, configure your VPN to use a reliable DNS server or enable its "DNS leak protection" setting.
If the error affects everyone worldwide (not just your device), the domain itself may have expired or its DNS records may have been deleted. Check the domain's WHOIS record and DNS status:
# Check if domain resolves from an external DNS server
nslookup example.com 8.8.8.8
# Check WHOIS expiry
whois example.com | grep -i expirERR_NAME_NOT_RESOLVED caused by an expired domain or deleted DNS record can take down your site for hours before you notice. Alive24x7 monitors your DNS records continuously and alerts you the moment something changes — so you fix it before your users see the error.
Start Free DNS Monitoring