Fix ERR_NAME_NOT_RESOLVED by Replacing Broken DNS Settings

If you see ERR_NAME_NOT_RESOLVED in Chrome, it means your computer could not translate a website’s name (like example.com) into an IP address. The fix often involves replacing broken DNS settings—either by flushing the DNS cache, changing to a public DNS server, or resetting network settings. This guide walks through the exact steps and explains why they work.

What Causes ERR_NAME_NOT_RESOLVED

This error appears when the Domain Name System (DNS) lookup fails. DNS is the internet’s phonebook: it converts human-friendly names into numeric IP addresses. When that conversion fails, the browser cannot connect to the server, and you see the error. Common causes include:

Incorrect or outdated DNS server addresses in your network adapter settings.
A corrupted DNS cache stored on your PC.
Flaky Wi-Fi or Ethernet connection.
Router or modem issues.
Firewall or antivirus blocking DNS requests.
Malware or browser extensions interfering.

Sometimes the problem is on the website’s side, but before assuming that, it’s worth checking your own DNS configuration.

How DNS Settings Work in Windows

Windows uses the DNS servers you specify (or those assigned automatically by your router) to resolve domain names. Your router typically gets DNS servers from your Internet Service Provider (ISP). If those servers are slow, down, or misconfigured, you’ll see resolution errors. You can override them by setting a public DNS server like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1) directly in your network adapter settings. Windows also maintains a local cache of previous DNS lookups; if that cache gets corrupted, it can cause errors even when the DNS servers are fine.

Step-by-Step Fix: Replace Broken DNS Settings

Follow these steps in order. Most users resolve the issue with steps 1–3.

Flush the DNS cache. Open Command Prompt as administrator (search “cmd”, right-click, “Run as administrator”) and type: ipconfig /flushdns. Press Enter. This clears the local cache.
Change DNS servers to a public provider. Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your active connection (Wi-Fi or Ethernet) and select Properties. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Choose “Use the following DNS server addresses” and enter:
- Preferred: 8.8.8.8
- Alternate: 8.8.4.4
Click OK and close all windows.
Renew the IP address. In the same Command Prompt window, type ipconfig /release then ipconfig /renew. This forces your PC to request a fresh IP address from the router.
Reset the network stack. In Command Prompt (admin), run these commands one by one:
- netsh winsock reset
- netsh int ip reset
Restart your PC afterward.
Check the hosts file. Open Notepad as administrator, then open C:\Windows\System32\drivers\etc\hosts. Look for any lines that map a domain to 127.0.0.1 or another IP. If you see entries for the site you’re trying to visit, delete them (unless you added them intentionally). Save the file.
Disable proxy settings. In Windows Settings, go to Network & Internet > Proxy. Ensure “Use a proxy server” is off (unless you actually use a proxy). Some VPNs or extensions set a proxy automatically.
Restart your router. Unplug it for 30 seconds, then plug it back in. This clears the router’s own DNS cache and re-establishes the connection.

How to Choose a DNS Server

If you decide to change DNS servers, you have several reliable options. Google Public DNS (8.8.8.8 and 8.8.4.4) is widely used and fast. Cloudflare (1.1.1.1 and 1.0.0.1) emphasizes privacy and speed. Quad9 (9.9.9.9) blocks malicious domains. You can also use your ISP’s DNS if it’s working, but public servers often resolve errors caused by ISP outages. There is no single “best” choice; try one and if it doesn’t work, switch to another. You can also test with nslookup example.com in Command Prompt to see which server responds.

Common Mistakes and Misconceptions

One common mistake is forgetting to restart the PC after changing DNS settings—sometimes the old settings linger until a reboot. Another is editing the hosts file incorrectly, which can cause more errors. People also assume the error is always on their end, but it can be a temporary outage on the website’s DNS. A quick check: open Command Prompt and type ping google.com. If that resolves, your DNS works; the problem might be with the specific site. If even Google fails, your DNS is likely broken.

When to Try Alternative Fixes

If the steps above don’t work, try these:

Disable IPv6 temporarily. In the same adapter properties, uncheck Internet Protocol Version 6 (TCP/IPv6) and restart. Some routers mishandle IPv6 DNS.
Run Windows Network Diagnostics. Right-click the network icon in the taskbar and select “Troubleshoot problems.”
Update your network adapter driver. Go to Device Manager, expand “Network adapters,” right-click your adapter, and choose “Update driver.”
Scan for malware. A malicious program can alter DNS settings. Use Windows Defender or a trusted third-party scanner.
Try a different browser or device. If the error only appears in Chrome, reset Chrome’s settings (Settings > Advanced > Reset and clean up). If it appears on all devices, the problem is likely your router or ISP.

Frequently Asked Questions

Why does ERR_NAME_NOT_RESOLVED happen only in Chrome?

Chrome uses its own DNS cache and sometimes has a bug. Try clearing Chrome’s cache (Settings > Privacy and security > Clear browsing data) or resetting Chrome flags. If the error persists in other browsers, the issue is system-wide.

Is it safe to use public DNS servers like 8.8.8.8?

Yes, public DNS servers are generally safe and often more reliable than ISP servers. They do see your DNS queries, so if privacy is a concern, use a service like Cloudflare that logs less. They do not see your actual web traffic.

Will changing DNS settings affect my internet speed?

It can, but usually minimally. A faster DNS server can speed up the initial connection to websites, but it won’t increase your download or upload bandwidth. The effect is most noticeable when visiting many different sites.

How do I know if the problem is on my side or the website’s?

Try accessing the site on your phone using cellular data (not Wi-Fi). If it loads, the problem is likely your network or DNS. You can also use a public DNS checker tool online, but the phone test is the simplest.

What does “flush DNS” actually do?

It clears the local cache that Windows keeps of recent DNS lookups. If that cache is corrupted or contains outdated entries, flushing forces your PC to query the DNS server fresh, which often resolves the error.

I changed DNS settings but still get the error. What next?

Try the full reset commands (netsh winsock reset, netsh int ip reset) and restart. If that fails, check your router’s DNS settings—log into the router admin page and set the DNS there as well. If the problem persists across all devices, contact your ISP.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →