First, confirm that the URL input is correct, other websites are accessible and the device network is normal, and troubleshoot the website itself or network connection problems; 2. Restart the router and modem to resolve temporary network failures; 3. Clear Chrome's DNS cache, click "Clear host cache" on the chrome://net-internals/#dns page and refresh the socket pool; 4. Change the DNS server to Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1) to improve resolution stability; 5. Clean the system DNS cache, Windows users run ipconfig /flushdns, /release, /renew and netsh winsock reset at the administrator command prompt, and macOS users use sudo dscacheutil -flushcache and sudo killall -HUP mDNSResponder, Linux users execute sudo systemd-resolve --flush-caches; 6. Disable all Chrome extensions and clear browsing data (including cookies and cache files) to eliminate browser interference; 7. Temporarily close the firewall or antivirus software to determine whether DNS requests are blocked due to security software; 8. Use other browsers or Chrome invisible mode to confirm whether it is a browser configuration problem; 9. Check whether the system hosts file (path is C:\Windows\System32\drivers\etc\hosts or /etc/hosts) to see if there is manual blocking or redirecting rules for the target domain name, and if so, comment or delete it; 10. If the above steps are invalid, go through Down For Tools such as Everyone Or Just Me confirm whether the website itself is faulty. If so, you need to wait for it to recover; this error is usually caused by a failure in DNS resolution. Performing the above steps in sequence can solve most cases, and the problem can be fixed in the end.

The ERR_NAME_NOT_RESOLVED error in Google Chrome means your browser can't find the website's server because the domain name can't be translated into an IP address. This is usually a DNS-related issue, but it can also stem from your network settings, browser, or even the website itself. Here's how to fix it step by step.

1. Check the Website and Internet Connection

Before diving into technical fixes, rule out the basics:

• ? Make sure you typed the URL correctly (eg, no extra characters or wrong domain like .cmo instead of .com ).
• ? Test if other websites load. If they don't, the issue is likely with your internet connection.
• ? Try opening the site on another device using the same network. If it fails there too, the problem may be network-wide.

Tip: You can also try accessing the site via a mobile data connection or a public Wi-Fi hotspot to confirm if it's reachable.

2. Restart Your Router and Modem

Sometimes, the issue is temporary and caused by a glitch in your router or ISP.

• Turn off your router and modem.
• Wait 30 seconds.
• Turn them back on and wait for all lights to stabilize.
• Reload the page in Chrome.

This often clears up temporary DNS or connection hiccups.

3. Clear Chrome's DNS Cache

Chrome maintains its own DNS cache, which can become outdated or corrupted.

Steps:

1. Open Chrome and go to:
   chrome://net-internals/#dns
2. Click the "Clear host cache" button.

Then try reloading the problematic site.

Bonus: Also clear socket pools at chrome://net-internals/#sockets by clicking "Flush socket pools" — this helps reset active connections.

4. Change Your DNS Server

Your current DNS (Domain Name System) server might be slow or unresponsive. Switching to a reliable one like Google DNS or Cloudflare can help.

Use Google DNS:

1. Go to Control Panel > Network and Sharing Center > Change adapter settings .
2. Right-click your active network connection → Properties .
3. Select "Internet Protocol Version 4 (TCP/IPv4)" → Properties .
4. Choose "Use the following DNS server addresses" and enter:
   • Preferred DNS server: 8.8.8.8
   • Alternate DNS server: 8.8.4.4
5. Click OK , then restart your browser.

Alternatively, use Cloudflare DNS : 1.1.1.1 and 1.0.0.1 .

5. Flush Your System DNS Cache

Your operating system also caches DNS entries. Clear it:

On Windows:

1. Open Command Prompt as Administrator.
2. Run these commands one by one:

    ipconfig /flushdns
   ipconfig /release
   ipconfig /renew
   netsh winsock reset

3. Restart your computer.

On macOS: Open Terminal and run:

 sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

On Linux (Ubuntu/Debian):

 sudo systemd-resolve --flush-caches

6. Disable Extensions and Clear Browser Data

A misbehaving Chrome extension or corrupted cookies might interfere.

• Go to chrome://extensions/ and disable all extensions temporarily.
• Test the site again.
• If it works, re-enable extensions one by one to find the culprit.

Also, clear browser data:

• Press Ctrl Shift Del (Windows) or Cmd Shift Del (Mac).
• Select "All time" and check cookies , Cached images and files .
• Click Clear data .

7. Temporarily Disable Firewall or Antivirus

Some security software blocks DNS requests or filters traffic too aggressively.

• Turn off your firewall or antivirus temporarily.
• Check if the site loads.
• If it works, adjust the security settings or consider switching to a less intrusive tool.

Don't leave your system unprotected — only disable temporarily for testing.

8. Try Another Browser or Incognito Mode

Test the same site in Firefox, Edge, or Chrome Incognito ( Ctrl Shift N ).
If it works in incognito, the issue is likely tied to Chrome's profile, extensions, or cache.

9. Check Hosts File for Manual Overrides (Advanced)

Your computer's hosts file might be redirecting or blocking the domain.

• File location:
  C:\Windows\System32\drivers\etc\hosts (Windows)
  /etc/hosts (macOS/Linux)

• Open it with Notepad (as admin if on Windows).

• Look for any lines containing the problematic domain.

• Remove or comment them out by adding # at the start.

• Save and restart your browser.

10. Wait It Out (If the Site Is Down)

Sometimes the website itself has DNS propagation issues or server downtime.

• Use tools like Down For Everyone Or Just Me or DNS Checker to verify.
• If others can't access it either, the problem is on the site's end — just wait.

Fixing ERR_NAME_NOT_RESOLVED usually comes down to DNS or local network issues. Start with clearing Chrome's cache and restarting your router, then move to changing DNS settings if needed. Most cases are resolved within a few minutes.

Basically, it's not as scary as it looks — just a hiccup in how your computer finds websites.

The above is the detailed content of How to fix ERR_NAME_NOT_RESOLVED in Google Chrome?. For more information, please follow other related articles on the PHP Chinese website!