How To Fix ERR_NAME_NOT_RESOLVED Error On Google Chrome

Few things are more frustrating than typing a website address into Chrome and being greeted by a blank page that says “This site can’t be reached” followed by the cryptic code ERR_NAME_NOT_RESOLVED. The good news is that this error is almost always fixable on your end, and most solutions take less than five minutes.

This guide walks you through every known fix for the ERR_NAME_NOT_RESOLVED error on Windows, Mac, Android, and iOS — starting with the simplest solutions and working toward more advanced troubleshooting.

What Does ERR_NAME_NOT_RESOLVED Mean?

Every website you visit has a numerical IP address behind it, something like 104.26.10.230. When you type a domain name like google.com into your browser, the Domain Name System (DNS) translates that human-readable name into the correct IP address so Chrome can connect to the server hosting the site.

ERR_NAME_NOT_RESOLVED means Chrome tried to look up the IP address for the domain you entered and failed. Without the IP address, the browser has nowhere to go, so the page refuses to load entirely.

This is not the same as a slow-loading page or a timeout error. It means the very first step of the connection — finding the address — broke down before anything else could happen.

What Causes the ERR_NAME_NOT_RESOLVED Error?

Before jumping into fixes, it helps to understand the most common causes so you can narrow down the problem faster.

Cause	What’s Happening
Typo in the URL	You misspelled the domain name or used .con instead of .com
Corrupted DNS cache	Your computer or browser stored an outdated or broken IP address for the site
DNS server is down	The DNS server assigned by your ISP is temporarily unavailable or slow
Network connection issues	Your Wi-Fi dropped, your Ethernet cable is loose, or your router needs a restart
Chrome’s page preloading	Chrome’s prediction feature stored outdated DNS data for a linked page
Firewall or antivirus blocking	Security software is intercepting or blocking DNS queries on port 53
Incorrect hosts file entries	Manual IP mappings in your system’s hosts file are pointing to the wrong address
VPN or proxy interference	A VPN or proxy is routing DNS queries through a server that can’t resolve the domain
DNSSEC misconfiguration	The domain’s security extensions are misconfigured, often after a hosting migration
The website itself is down	The domain’s DNS records are missing, expired, or the server is offline

In most cases, the problem is on your device or network, not the website. The fixes below are ordered from quickest to most involved.

Fix 1: Check the URL for Typos

This sounds obvious, but it catches more people than you’d expect. A single wrong letter, a missing hyphen, or typing .con instead of .com is enough to trigger the error. Double-check the address bar carefully.

Also try adding or removing “www.” from the beginning of the URL. Some domains are configured to work with one but not the other.

If you’re not sure you have the right URL, search for the website name in Google and click the result from there instead of typing the address manually.

Fix 2: Check Your Internet Connection

Before you start changing settings, make sure you’re actually connected to the internet.

Open a new tab and try visiting a completely different website. If multiple sites fail, the issue is your connection, not a specific domain. Try these quick checks:

• Look at your Wi-Fi icon — is it connected or showing a warning symbol?
• If you’re on Wi-Fi, try switching to mobile data (or vice versa) to see if the error follows
• Open Command Prompt (Windows) or Terminal (Mac) and run ping google.com to test basic connectivity
• Try the same website on a different device connected to the same network

If no sites load on any device, the problem is your router or ISP. If the error only appears on one device, the problem is local to that machine.

Fix 3: Restart Your Router

Routers can develop temporary glitches that interfere with DNS resolution. A simple restart clears the router’s internal DNS cache and re-establishes the connection to your ISP’s DNS servers.

Unplug your router’s power cable, wait at least 30 seconds, then plug it back in. Wait for the internet/DSL indicator light to turn solid green before testing again. This alone fixes the problem more often than most people expect.

Fix 4: Clear Chrome’s Browser Cache and Cookies

Chrome stores cached versions of websites you’ve visited, including DNS-related data. When this cached data becomes outdated or corrupted, it can prevent Chrome from resolving domain names correctly.

To clear your browsing data in Chrome:

1. Click the three-dot menu in the top-right corner
2. Go to Settings → Privacy and Security → Delete Browsing Data
3. Set the time range to All Time
4. Check both Cookies and other site data and Cached images and files
5. Click Delete Data

Restart Chrome and try loading the site again.

On mobile (Android or iOS), you’ll find the clear browsing data option under the three-dot menu → History → Delete Browsing Data instead of the Settings path.

Fix 5: Clear Chrome’s Internal DNS Cache

Chrome maintains its own DNS cache separate from your operating system’s cache. Even if you clear your browsing data, Chrome’s internal DNS cache can still hold stale entries.

To flush Chrome’s DNS cache:

1. Open a new tab in Chrome
2. Type chrome://net-internals/#dns in the address bar and press Enter
3. Click the Clear Host Cache button

This forces Chrome to perform fresh DNS lookups for every domain instead of relying on cached records. No restart required — just try visiting the site again immediately.

Fix 6: Flush Your Operating System’s DNS Cache

Your operating system also maintains a DNS cache independently from Chrome. Flushing it removes all stored DNS records and forces your computer to request fresh information from the DNS server.

On Windows:

Open Command Prompt as Administrator (right-click the Start button → Terminal or Command Prompt as Admin) and run:

ipconfig /flushdns

You should see a confirmation message that the DNS resolver cache was successfully flushed.

For a more thorough network reset, run these commands one after another:

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

Restart your computer after running these commands.

On Mac:

Open Terminal and run:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your admin password when prompted.

On Linux:

Open Terminal and run:

sudo systemd-resolve --flush-caches

Or if you’re using an older distro:

sudo /etc/init.d/nscd restart

Fix 7: Change Your DNS Server to Google or Cloudflare

Your ISP assigns DNS servers automatically, but these servers can be slow, overloaded, or temporarily down. Switching to a reliable public DNS provider often fixes DNS resolution errors instantly.

The two most popular choices are:

Provider	Primary DNS	Secondary DNS
Google DNS	8.8.8.8	8.8.4.4
Cloudflare DNS	1.1.1.1	1.0.0.1

On Windows:

1. Right-click the Start button → Network Connections (or search for “Network Connections” in Settings)
2. Click Change adapter options or Advanced network settings
3. Right-click your active network adapter (Wi-Fi or Ethernet) → Properties
4. Select Internet Protocol Version 4 (TCP/IPv4) → click Properties
5. Select Use the following DNS server addresses
6. Enter 8.8.8.8 as the Preferred DNS and 8.8.4.4 as the Alternate DNS
7. Check Validate settings upon exit and click OK

On Mac:

1. Open System Settings → Network
2. Click your active connection (Wi-Fi or Ethernet) → Details or Advanced
3. Go to the DNS tab
4. Click the + button to add 8.8.8.8 and 8.8.4.4
5. Click OK and Apply

On Android:

1. Go to Settings → Network & Internet → Advanced → Private DNS
2. Select Private DNS provider hostname
3. Enter dns.google and tap Save

On your router (applies to all connected devices):

1. Open your browser and go to 192.168.1.1 or 192.168.0.1 (your router’s admin page)
2. Find the DNS settings (usually under WAN, Internet, or DHCP settings)
3. Replace the existing DNS server addresses with 8.8.8.8 and 8.8.4.4
4. Save and restart your router

After changing DNS, flush your DNS cache (Fix 6) and restart Chrome.

Fix 8: Disable Chrome’s Page Preloading Feature

Chrome has a prediction feature that preloads pages you might click on next, including their DNS information. While this speeds up browsing in theory, it can store outdated DNS data that triggers the ERR_NAME_NOT_RESOLVED error.

To disable it:

1. Open Chrome → click the three-dot menu → Settings
2. Go to Privacy and Security
3. Click Cookies and other site data (or Preload pages depending on your Chrome version)
4. Find the Preload pages for faster browsing and searching option
5. Turn it off

Restart Chrome and check whether the error is resolved.

Fix 9: Restart the DNS Client Service (Windows Only)

Windows runs a background service called the DNS Client that handles all DNS resolution. If this service freezes or crashes, no website will resolve — you’ll get ERR_NAME_NOT_RESOLVED on every site.

To restart it:

1. Press Win + R, type services.msc, and press Enter
2. Scroll down to find DNS Client
3. Right-click it and select Restart

If the Restart option is greyed out, you can restart it via Command Prompt instead:

net stop dnscache
net start dnscache

Fix 10: Temporarily Disable Your Firewall or Antivirus

Firewalls and antivirus software can block DNS queries, especially on port 53, which prevents domain names from being resolved. This is particularly common with aggressive security suites that filter all network traffic.

Temporarily disable your firewall or antivirus, then try loading the website again. If the site loads successfully, you’ve found the culprit. You’ll need to add an exception in your security software for DNS traffic or switch to a less aggressive alternative.

On Windows, you can temporarily disable the built-in firewall:

1. Open Windows Security → Firewall & Network Protection
2. Click your active network profile
3. Toggle Microsoft Defender Firewall off temporarily
4. Test the website
5. Turn the firewall back on immediately after testing

Do not leave your firewall disabled permanently.

Fix 11: Check and Edit the Hosts File

Your operating system has a hosts file that can manually map domain names to IP addresses, overriding DNS entirely. If this file contains incorrect or outdated entries — sometimes left by malware — it can cause ERR_NAME_NOT_RESOLVED for specific sites.

On Windows:

The hosts file is located at C:\Windows\System32\drivers\etc\hosts. Open it with Notepad running as Administrator. The default file should only contain comment lines starting with # and possibly a localhost entry. If you see any suspicious entries mapping domain names to IP addresses like 0.0.0.0 or 127.0.0.1, remove them, save the file, and restart Chrome.

On Mac and Linux:

The hosts file is at /etc/hosts. Open Terminal and edit it with:

sudo nano /etc/hosts

Look for and remove any incorrect entries, then save with Ctrl+O and exit with Ctrl+X.

On Android (rooted devices only):

The hosts file is at /system/etc/hosts. By default it should only contain localhost 127.0.0.1. Remove any other entries that don’t belong.

Fix 12: Disable VPN or Proxy

VPNs and proxy servers route your traffic through different servers, which can interfere with DNS resolution. Some VPNs use their own DNS servers that may not resolve all domains correctly, and proxy configurations can redirect DNS queries in ways that break resolution.

If you’re using a VPN, temporarily disconnect it and try the website again. If it loads, the problem is with your VPN’s DNS handling. Most VPN apps allow you to configure custom DNS servers within the app settings — switch to 8.8.8.8 or 1.1.1.1 inside your VPN configuration.

For proxy settings on Windows, go to Settings → Network & Internet → Proxy and make sure no proxy is enabled unless you intentionally configured one.

Fix 13: Reset Chrome to Default Settings

If the error persists after trying everything above, something in Chrome’s configuration may be corrupted. Resetting Chrome to its default settings clears all extensions, custom settings, and cached data without deleting your bookmarks or saved passwords.

1. Open Chrome → three-dot menu → Settings
2. Click Reset settings in the left sidebar (or navigate to chrome://settings/reset)
3. Click Restore settings to their original defaults
4. Confirm by clicking Reset settings

Restart Chrome and test the website.

Fix 14: Run a Malware Scan

Malware can alter your DNS settings, modify your hosts file, or redirect DNS queries to malicious servers — all of which cause ERR_NAME_NOT_RESOLVED. If none of the above fixes work, especially if the problem appeared suddenly, malware may be the cause.

On Windows, run a full scan using Windows Security (or your preferred antivirus). Go to Windows Security → Virus & Threat Protection → Scan Options and select Full Scan. If malware is found and removed, flush your DNS cache and restart your computer before testing again.

Fix 15: Disable DNSSEC (For Website Owners Only)

If you own the website that’s showing the error — especially if you recently migrated hosting, transferred the domain, or changed nameservers — the cause may be a DNSSEC misconfiguration.

DNSSEC (Domain Name System Security Extensions) adds cryptographic authentication to DNS records. When domain settings change, the DNSSEC signatures may no longer match, which causes DNS resolution to fail entirely.

To fix this, disable DNSSEC through your domain registrar’s control panel, wait for DNS propagation (up to 48 hours), and then re-enable it with fresh signatures after the migration is complete.

How To Fix ERR_NAME_NOT_RESOLVED on Android

Android devices can experience this error in both Chrome and other apps that rely on web connections, including the Google Play Store. In addition to the general fixes above, try these Android-specific solutions:

Change Private DNS: Go to Settings → Network & Internet → Advanced → Private DNS. Select “Private DNS provider hostname” and enter dns.google. Tap Save.

Clear Chrome app cache: Go to Settings → Apps → Chrome → Storage → Clear Cache. This is separate from clearing browsing data within Chrome itself.

Disable preloading in mobile Chrome: Open Chrome → three-dot menu → Settings → Privacy and Security → Preload Pages → set to Off.

Boot into Safe Mode: Hold the power button, then long-press “Power Off” until the Safe Mode option appears. If the error disappears in Safe Mode, a recently installed app is interfering with DNS resolution.

Reset network settings: Go to Settings → System → Reset Options → Reset Wi-Fi, Mobile & Bluetooth. This restores all network settings to factory defaults without erasing your data.

Factory-reset the Chrome app: Go to Settings → Apps → Chrome → Disable. Confirm the action to restore Chrome to its factory version. Re-enable it afterward and test.

How To Fix ERR_NAME_NOT_RESOLVED on Mac

Mac users can follow most of the general fixes above, but the DNS flushing and DNS server change processes differ slightly.

Flush DNS cache on Mac: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your admin password when prompted.

Change DNS servers on Mac: Open System Settings → Network → select your active connection → Details → DNS tab. Click the “+” button to add new DNS server addresses like 8.8.8.8 and 1.1.1.1.

Check the hosts file: Run sudo nano /etc/hosts in Terminal. Remove any suspicious entries, save, and restart Chrome.

When the Problem Isn’t on Your End

If you’ve tried every fix above and the error only appears for one specific website, the issue is likely on the website’s side. The domain may have expired, the DNS records may be misconfigured, or the hosting server may be down.

You can verify this by checking whether the site loads for other people using a free tool like “downforeveryoneorjustme.com” or by testing from a different network entirely (such as your phone on mobile data).

If the website is yours, check your domain registrar to confirm the domain hasn’t expired and that your nameservers are pointing to the correct hosting provider. If you recently changed hosting or transferred the domain, allow up to 48 hours for DNS propagation to complete worldwide.

Quick Reference: ERR_NAME_NOT_RESOLVED Fixes Summary

Fix	Time to Complete	Difficulty
Check URL for typos	10 seconds	Easy
Check internet connection	1 minute	Easy
Restart router	2 minutes	Easy
Clear Chrome cache and cookies	1 minute	Easy
Clear Chrome’s internal DNS cache	30 seconds	Easy
Flush system DNS cache	1 minute	Easy
Change DNS server	3 minutes	Moderate
Disable Chrome page preloading	1 minute	Easy
Restart DNS Client service	1 minute	Easy
Disable firewall/antivirus temporarily	2 minutes	Moderate
Check and edit hosts file	3 minutes	Moderate
Disable VPN or proxy	1 minute	Easy
Reset Chrome to defaults	2 minutes	Easy
Run malware scan	10-30 minutes	Easy
Disable DNSSEC (site owners)	5 minutes	Advanced

Most users will solve the problem within the first five or six fixes on this list. Start from the top and work your way down — there’s no need to jump to advanced solutions before ruling out the simple ones.