How to Fix ERR_NAME_NOT_RESOLVED in Google Chrome (Permanent Fix)
Switch your network DNS to Google Public DNS (8.8.8.8 and 8.8.4.4) and run 'ipconfig /flushdns' in Command Prompt.
Preliminary Fast Checks
Verify these 3 simple prerequisites before proceeding to in-depth fixes:
đŦ Root Cause: Why Does ERR_NAME_NOT_RESOLVED Occur?
When you type a domain (e.g. kravi.org), your system asks a DNS resolver for its numerical IP address. ERR_NAME_NOT_RESOLVED indicates that your configured DNS servers failed to return any valid A or AAAA records. This is usually caused by ISP DNS outages, local cache corruption, or malware tampering with the hosts file.
đ Primary Triggers for ERR_NAME_NOT_RESOLVED
- ISP DNS servers experiencing outage or query drops.
- Corrupted Windows DNS Client resolver cache.
- Malware adding redirect entries to C:\Windows\System32\drivers\etc\hosts.
- Conflicting VPN split-tunneling configurations.
What NOT to Do
Do not edit system hosts files without creating a backup first.
Complete Step-by-Step Solutions for ERR_NAME_NOT_RESOLVED
Execute these verified methods sequentially from easiest to most advanced:
Change to Google or Cloudflare DNS
Bypass unreliable ISP DNS servers with high-speed global anycast resolvers.
Go to Windows Settings > Network & Internet > Advanced network settings > click your Wi-Fi/Ethernet > Edit DNS. Set Preferred to 8.8.8.8 and Alternate to 8.8.4.4 (or Cloudflare: 1.1.1.1).
Flush DNS Resolver Cache
Clear corrupted domain mappings instantly.
ipconfig /flushdns
Open Command Prompt as Administrator, paste the command, press Enter.
Reset Chrome Flags to Default
Experimental browser networking flags can break DNS resolution.
Navigate to chrome://flags in Chrome, click 'Reset all' at the top right, and click 'Relaunch'.
đĄ How to Prevent ERR_NAME_NOT_RESOLVED In the Future
- Configure reliable DNS servers directly on your home router.
- Clear browser browsing data every few months.
Frequently Asked Questions
If it only affects one site while all others work, the domain owner's DNS records may have expired or are misconfigured on their hosting nameservers.