Google Chrome shows the ERR_NAME_NOT_RESOLVED error when it cannot translate a website’s human-readable name into the numeric IP address of its server. This critical translation is handled by the Domain Name System (DNS). When the lookup comes back completely empty, Chrome fails to open a connection, leaving the web page blank. Most cases originate on the visitor’s side due to stale cached records or a stuck network router, but site owners can also encounter the issue following incorrect DNS configurations, wrong nameservers, or an expired domain. The troubleshooting steps and details below reflect current network management guidelines.
What Is the ERR_NAME_NOT_RESOLVED Error?
Every website lives at a specific numeric IP address. DNS pairs the domain name you type into your browser with that number, functioning much like a phone contact list pairs a person’s name with their digital phone digits. Within Chromium’s network error architecture, this specific failure receives the error code -105, which is officially defined as a host name that could not be resolved. Because Brave and Edge operate on the Chromium engine, they print this exact error code, while Firefox reports a “Server Not Found” message for the identical underlying fault, and Safari uses its own proprietary wording. Despite the varying terminology across web browsers, they all point to the same root problem: the browser never learned where the target website actually lives on the internet.
Common Causes for Visitors and Site Owners
Determining whether the error stems from your local browsing environment or the target server is the fastest way to begin troubleshooting. If a website loads successfully on mobile data or on an entirely separate device, the problem is localized to your machine or network. If the site fails to load everywhere, the issue lies with the domain configuration. An offline device will trigger a different message, such as net::err_internet_disconnected, before any DNS lookup can even begin.
| Side | Cause | What happens |
|---|---|---|
| Visitor | Stale cached lookups | Chrome heads to an old, dead IP address. |
| Visitor | Modem-router glitch | The router keeps serving faulty ISP lookups. |
| Visitor | ISP block | Some domains get stopped, at times by regional restrictions. |
| Visitor | Proxy or VPN | Queries get misrouted or delayed. |
| Visitor | Android Private DNS | An unreachable resolver breaks every application. |
| Owner | Wrong A, AAAA, or CNAME records | The domain name points somewhere incorrect. |
| Owner | Cloudflare settings | Bad proxy options or failed server contact. |
| Owner | Lapsed registration | The registrar pulls the nameservers offline. |
| Owner | DNSSEC mistake | Faulty keys block lookups despite correct records. |
| Owner | Propagation | New edits can take up to two days to reach everyone. |
8 Steps to Fix ERR_NAME_NOT_RESOLVED (Visitor Guide)
If you are an internet user struggling to access a specific webpage, follow this sequential troubleshooting guide to resolve client-side caching and network lookup failures.
- Recheck the Address: One extra letter, a missing character, or the wrong domain extension leads nowhere. Typing
gooogle.cominstead ofgoogle.comis enough to trigger the error. - Power Cycle the Modem-Router: Unplug your networking hardware, wait 30 seconds, and plug it back in. Refresh the webpage once the connection is restored. On a Chromebook, identical router trouble can occasionally show up as a DHCP lookup failed error rather than a standard DNS code.
- Flush the DNS Cache on Windows, macOS, and Linux: Clearing your operating system‘s DNS resolver cache removes outdated or corrupted network mappings.
System Command Then Windows ipconfig /flushdns, thennetsh winsock resetRestart your PC. (The winsock reset rebuilds Windows networking software; skipping the restart prevents it from taking effect). macOS sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderEnter your administrator password when prompted. Linux resolvectl flush-cachesCache statistics should read zero. - Clear Chrome’s Own Host Cache: Google Chrome stores DNS answers separately from the operating system. Navigate to
chrome://net-internals/#dnsin your address bar and press Clear host cache. Next, open the Sockets tab and press Flush socket pools to close stale connections, then relaunch Chrome. - Switch to 1.1.1.1 or 8.8.8.8: Internet Service Provider (ISP) resolvers can fail, lag under heavy load, or intentionally block websites. Cloudflare operates 1.1.1.1 and Google operates 8.8.8.8, both of which are free public alternatives.
- Windows 11: Go to Settings > Network & internet > Wi-Fi or Ethernet > DNS server assignment > Edit. Choose Manual, turn on IPv4, enter one resolver, and save.
- Mac (Ventura and newer): Go to System Settings > Network > your connection > Details > DNS. Press +, add the resolver, and confirm with OK.
- ChromeOS: Go to Settings > Network > your network > Network, then set Name servers to Custom.
- Check Chrome’s Secure DNS and Preload Settings: Secure DNS sends lookups over HTTPS to a provider of your choice. If that provider is unreachable, domain names will fail even on an active connection. Go to Settings > Privacy and security > Security, find Use secure DNS, and set it to your current service provider or switch it off for testing purposes. Additionally, type “preload” into the settings search box and turn off page preloading.
- Pause the VPN, Proxy, or Antivirus: A slow or strict Virtual Private Network server disrupts lookups. Certain antivirus programs also introduce DNS monitors that block safe queries. Turn each tool off briefly and reload the page. If the page opens, change your VPN region or whitelist the site. School and work Chromebooks frequently route through a proxy; you can switch the proxy off in network settings if the device is unmanaged. (Note: A VPN that drops mid-session can leave a leftover proxy entry behind, though that usually surfaces as an
ERR_TUNNEL_CONNECTION_FAILEDerror instead). - Remove the Site from the Hosts File: The local hosts file overrides DNS. A site mapped there to an unused IP address will never load.
- Windows: Open Notepad as an administrator, choose File > Open, and paste
C:WindowsSystem32driversetc. Set the file filter to show all files, open thehostsfile, delete the offending site’s line, and save. - Mac: Run
sudo nano /private/etc/hostsin the terminal and enter your password. Delete the target line, then press Control + O, Enter, and Control + X.
- Windows: Open Notepad as an administrator, choose File > Open, and paste
Fixing the Error on Android Devices
Android’s Private DNS setting pushes every application through a single resolver. When that specific resolver goes down, application network access drops entirely. Open Settings > Network & internet > Private DNS and switch the configuration to Automatic or Off. If you remain stuck, toggle Airplane mode on and off, and clear Chrome’s mobile application cache. Temporarily moving from Wi-Fi to mobile data functions as an effective stopgap, though a lasting fix still requires a cache flush or updated DNS settings.
Site Owner Fixes: When the Problem Is Global
If every visitor encounters the ERR_NAME_NOT_RESOLVED error when visiting your domain, the root cause is server-side and requires administrative intervention.
- A, AAAA, and CNAME Records Plus Nameservers: Each A record requires the correct IPv4 address supplied by your web host. Add AAAA records for IPv6 support, and point subdomain CNAME records at the appropriate targets. Migration errors and typos often leave nameservers misconfigured; enter them precisely as provided by your host, typically formatted as
ns1.yourhost.comandns2.yourhost.com. - Cloudflare’s Orange Cloud: An orange icon beside an A or CNAME record indicates that Cloudflare proxying is active. Click the icon once to turn it gray (DNS-only mode) and reload your site after a few minutes. If the site loads successfully, review your SSL settings or purge Cloudflare’s cache. If it still fails, contact your hosting provider.
- Expired Domains and DNSSEC Keys: Check your domain’s status and expiration date at your registrar, such as Namecheap. If you recently renewed it, allow several hours for processing. Furthermore, DNSSEC signs records using cryptographic keys; switching your web host or DNS provider without updating those keys will break resolution entirely. Disable DNSSEC, wait for the site to return online, create new DS records with your current host, and then re-enable DNSSEC.
- Propagation Up to 48 Hours: DNS edits usually propagate across the global network within hours, but they can take up to two full days. A mix of green checkmarks and red crosses on online checking tools indicates that your DNS changes are still moving across global root servers.
ERR_NAME_NOT_RESOLVED vs. Related Chrome Error Codes
While ERR_NAME_NOT_RESOLVED represents a general lookup failure, Chrome issues several other network error codes depending on the specific phase where the connection breaks down.
| Code | Meaning |
|---|---|
| DNS_PROBE_FINISHED_NXDOMAIN | Lookup finished; a definitive answer was returned that no such domain exists. |
| ERR_CONNECTION_TIMED_OUT | The target IP address was found, but the server replied too slowly. |
| ERR_CONNECTION_REFUSED | The server rejected Chrome’s connection attempt, often due to an active firewall or server downtime. |
| DNS_PROBE_FINISHED_NO_INTERNET | The device is offline, so the DNS lookup never began. |
Running a cache flush and switching to a public resolver resolves most of these related errors. If a server connects successfully but sends no data back, Chrome prints a separate code, which is typically addressed via net::err_empty_response troubleshooting guides.
Frequently Asked Questions
Is ERR_NAME_NOT_RESOLVED caused by a virus?
Rarely. Stale DNS data, active VPN connections, or strict firewall rules cause the vast majority of cases. However, malware can edit your local hosts file to intentionally block access to specific websites, so you should inspect that file if multiple domains fail simultaneously.
Why does ERR_NAME_NOT_RESOLVED appear on only one website?
An error affecting only a single site points to a stale cached record, an explicit hosts file entry for that domain, or broken DNS records managed on the website owner’s side. Loading the target site on mobile data can quickly help you distinguish between a local issue and a global server fault.
What fix do Reddit users recommend for ERR_NAME_NOT_RESOLVED?
Community threads on technology support subreddits most frequently suggest switching your DNS provider to 8.8.8.8 or 1.1.1.1, followed by executing an ipconfig /flushdns command. Turning off an active VPN client is also widely cited as the next most common remedy.
Why does the error continue after switching to 1.1.1.1?
Cloudflare’s resolver may occasionally experience an outage, or your specific ISP might block external public resolvers. Try switching to Google’s 8.8.8.8. If pages load successfully, the temporary fault originated with Cloudflare.
Does a VPN fix ERR_NAME_NOT_RESOLVED, as some Reddit posts claim?
Sometimes. A VPN routes your network lookups through alternative resolvers and bypasses a failing ISP server. Conversely, a slow or strict VPN can also trigger the error, which is why it is always recommended to test your connection with the VPN both enabled and disabled.































