home / browser errors / err-name-not-resolved

[ REPAIR GUIDE ] BROWSER ERRORS

How to fix ERR_NAME_NOT_RESOLVED

ERROR DETECTED >This site can't be reached. example.com's server IP address could not be found. ERR_NAME_NOT_RESOLVED

UPDATED NOVEMBER 20262 MIN READ9 FIXES

QUICK FIX

Check the spelling of the address, then restart your router and flush the DNS cache. If it still fails, switch to a different DNS server.

What it means

Your browser could not turn the website's name into an IP address, so it does not know where to connect. Either the name does not exist or has changed, or the DNS lookup on your device or network failed.

Common causes

  • A typo in the web address
  • The domain has expired, been removed or recently moved
  • A DNS problem on your router or internet provider
  • Stale DNS data cached on your device or in Chrome
  • A VPN, proxy or filter interfering with lookups
  • A changed hosts file on the computer

How to fix it

Work down the list. Each fix is safe to try before moving on to the next.

FIX 01Check the addressEASY

  1. Look carefully for typos, missing letters or a wrong ending such as .co instead of .com.
  2. Try the site on your phone using mobile data.
  3. If it fails everywhere, the domain may be down or no longer exist.

Why it helps: A mistyped name is the most common cause.

FIX 02Restart your router and deviceEASY

  1. Unplug the router for 30 seconds and plug it back in.
  2. Restart your computer or phone.
  3. Reload the page.

Why it helps: Refreshes the router's DNS connection to your provider.

FIX 03Clear Chrome's host cacheEASY

  1. Type chrome://net-internals/#dns in the address bar and press Enter.
  2. Select Clear host cache.
  3. Reload the site.

Why it helps: Removes old name lookups stored in the browser.

FIX 04Turn off VPN, proxy and filtersEASY

  1. Disconnect any VPN or DNS-filtering app.
  2. Windows 11: Settings > Network & internet > Proxy, turn off manual proxy settings you did not add.
  3. Reload the page.

Why it helps: These tools often handle DNS and can fail to look names up.

FIX 05Flush the DNS cache on your computerMEDIUM

  1. Windows: search cmd, right-click Command Prompt, choose Run as administrator, and run ipconfig /flushdns.
  2. Mac: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then type your Mac password when asked (nothing shows as you type) and press Return.
  3. Reload the page.

Why it helps: Clears saved lookups that may point to an old or missing address.

FIX 06Check Chrome's secure DNS settingMEDIUM

  1. Open More (three dots) > Settings > Privacy and security > Security.
  2. Scroll to Use secure DNS.
  3. If it is set to a custom provider, switch it back to the default option or turn it off, then reload.

Why it helps: A custom secure DNS provider that is unreachable will stop names resolving.

FIX 07Change your DNS serverMEDIUM

  1. Windows 11: open Settings > Network & internet. For Wi-Fi, select Wi-Fi, then your network's properties (or Hardware properties). For a cable, select Ethernet.
  2. Next to DNS server assignment select Edit, choose Manual, turn on IPv4, type the new addresses in Preferred DNS and Alternate DNS, and select Save.
  3. Mac: open System Settings > Network, select your connection, choose Details > DNS, add the servers with the + button, and select OK.
  4. Reload the page. To undo, set the DNS assignment back to Automatic (DHCP) on Windows or remove the added servers on Mac.

Why it helps: If your provider's DNS is failing, a different DNS server can resolve the name.

FIX 08Reset Windows network settingsADVANCED

  1. Warning: this removes and reinstalls network adapters; you may need to reconnect to Wi-Fi and reinstall VPN software.
  2. Run Command Prompt as administrator.
  3. Run netsh winsock reset and netsh int ip reset, then restart.
  4. If needed, use Settings > Network & internet > Advanced network settings > Network reset.

Why it helps: Repairs damaged network components that break DNS.

// RUN THIS SITE? FIXES FOR SITE OWNERS

FIX 09Check your domain's DNS recordsADVANCEDSITE OWNERS

  1. Make sure the domain registration has not expired.
  2. Check the domain uses the correct nameservers at the registrar.
  3. Confirm there is an A or AAAA record (or CNAME) for the exact hostname, including www.
  4. After changes, allow time for DNS caches to update.

Why it helps: Missing or wrong records mean nobody can find the site.

Check it's fixed

  • The site loads by name.
  • Other sites load quickly.
  • The site loads on another device on the same network.

When to get help

If many sites fail to resolve on every device, your internet provider's DNS may be down; contact them. If only your own domain fails, contact your registrar or DNS host.

Questions

What does "server IP address could not be found" mean?

It is the same problem as ERR_NAME_NOT_RESOLVED. The browser could not look up which server the website lives on.

Is ERR_NAME_NOT_RESOLVED the same as DNS_PROBE_FINISHED_NXDOMAIN?

They are closely related. Both mean the name lookup failed; NXDOMAIN specifically means the DNS answer said the name does not exist.

Why does it work on my phone but not my computer?

Your computer may have stale DNS data, a VPN, a proxy or a changed DNS setting. Flush DNS and check those settings.

Related fixes

Still stuck?

Paste the exact message and the repair bot will find the closest fix, or search it on Google, Microsoft, Apple, Reddit and YouTube.

Sources