Google Chrome Error Code ERR_NAME_NOT_RESOLVED: How to Fix It

Easy 10-20 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_NAME_NOT_RESOLVED
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-20 minutes
The ERR_NAME_NOT_RESOLVED error in Google Chrome occurs when your browser cannot translate a website's domain name into an IP address through DNS lookup. This common networking issue prevents you from accessing websites and can be caused by DNS server problems, corrupted browser data, or network configuration issues.
Ad

Tools You'll Need

How to Fix Error Code ERR_NAME_NOT_RESOLVED

  1. Check Your Internet Connection

  2. Clear Chrome's DNS Cache

  3. Flush Your Computer's DNS Cache

    You may need administrator privileges to run these commands.

  4. Change Your DNS Servers

    Write down your original DNS settings before changing them in case you need to revert.

  5. Restart Your Network Equipment

    Unplugging network equipment will temporarily disconnect all devices from the internet.

  6. Disable Antivirus and Firewall Temporarily

    Only disable security software temporarily for testing. Re-enable it immediately after testing.

  7. Reset Chrome's Network Settings

    This will reset all Chrome settings, remove extensions, and clear temporary data.

  8. Check Windows Hosts File

    Be very careful when editing the hosts file. Only remove entries you're certain about, as system entries are necessary for proper operation.
Ad

When to Call a Professional

Contact your internet service provider if the error persists after trying all steps, if it affects all devices on your network, or if you're uncomfortable editing system files. For business networks, contact your IT administrator as there may be corporate firewall or DNS policies in place.

Frequently Asked Questions

What causes ERR_NAME_NOT_RESOLVED in Chrome?
This error is caused by DNS lookup failures, meaning Chrome cannot translate domain names into IP addresses. Common causes include incorrect DNS server settings, corrupted DNS cache, firewall blocking, or temporary ISP DNS server issues.
Can I fix ERR_NAME_NOT_RESOLVED without changing DNS servers?
Yes, you can often fix this error by clearing Chrome's DNS cache, flushing your system's DNS cache, restarting your router, or temporarily disabling security software. Changing DNS servers is just one solution among several.
Why do some websites work while others show ERR_NAME_NOT_RESOLVED?
This happens when DNS cache contains outdated or corrupted entries for specific domains, or when certain websites are blocked by your DNS provider or security software. Your browser may have cached working DNS entries for some sites but not others.
Is ERR_NAME_NOT_RESOLVED the same as DNS_PROBE_FINISHED_NXDOMAIN?
These are related but different errors. ERR_NAME_NOT_RESOLVED means DNS lookup failed entirely, while DNS_PROBE_FINISHED_NXDOMAIN means the domain name doesn't exist. Both are DNS-related issues with similar troubleshooting steps.
Will changing DNS servers make my internet faster?
Changing to faster DNS servers like Google DNS or Cloudflare can slightly improve website loading times and may resolve connectivity issues, but the speed improvement is usually minimal compared to your actual internet connection speed.

Related Error Codes