How to Fix ERR_NAME_NOT_RESOLVED in Google Chrome

Attempting to navigate to a website in Google Chrome only to be stopped by the browser alert “This site can’t be reached. Check if there is a typo in [domain]. ERR_NAME_NOT_RESOLVED” halts browsing. The error code ERR_NAME_NOT_RESOLVED is an explicit Domain Name System (DNS) resolution failure: Google Chrome’s network stack attempted to translate the human-readable domain name (such as example.com) into a machine-routable IPv4 or IPv6 address, but received no valid DNS record from local caches or recursive upstream resolvers. When your operating system’s DNS cache contains stale records, local router DNS forwarders stall, or DNS over HTTPS (DoH) profiles deadlock, Chrome fails to establish the initial TCP socket connection. This guide provides comprehensive solutions to fix ERR_NAME_NOT_RESOLVED in Google Chrome.

What Causes ERR_NAME_NOT_RESOLVED in Chrome?

DNS resolution breakdowns originate from local client caches, router forwarders, and network configurations:

  • Corrupted Chrome Internal DNS Cache: Stagnant host resolver records or unclosed socket connections within Chrome’s internal network state.
  • Operating System DNS Resolver Cache Stalls: Outdated IP mappings in the Windows, macOS, or Linux local DNS client resolver.
  • Unresponsive ISP DNS Resolvers: Your internet service provider’s default recursive DNS servers suffering latency or downtime.
  • Misconfigured DNS over HTTPS (DoH): Chrome’s Secure DNS feature failing to negotiate encrypted DNS queries with Cloudflare, Google, or custom resolvers.
  • Firewall or Antivirus DNS Interception: Third-party security suites monitoring port 53 traffic and dropping UDP DNS query packets.

Method 1: Flush Chrome’s Internal Host Cache and Sockets

Google Chrome maintains an internal DNS resolver independent of the operating system. Flushing it removes dead host mappings.

  1. Open a new tab in Google Chrome.
  2. In the address bar, type the following internal URL and press Enter:
    chrome://net-internals/#dns
  3. Click the Clear host cache button.
  4. Next, navigate to:
    chrome://net-internals/#sockets
  5. Click Close idle sockets, then click Flush socket pools.
  6. Restart Chrome and reload the target website.

Method 2: Flush the Operating System DNS Cache

Purging local operating system resolver caches removes poisoned or outdated IP mappings.

  1. On Windows 11 / 10:
    • Press Win + S, type cmd, right-click Command Prompt, and select Run as administrator.
    • Flush the DNS cache:
      ipconfig /flushdns
    • Release and renew your IP address lease:
      ipconfig /release
      ipconfig /renew
    • Reset the Windows Winsock catalog:
      netsh winsock reset
    • Restart your computer.
  2. On macOS:
    • Open Terminal and run:
      sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
    • Enter your admin password and press Enter.

Method 3: Switch to Reliable Public DNS Servers (Google or Cloudflare)

Default ISP DNS servers frequently suffer routing timeouts. Switching to public Anycast resolvers ensures rapid lookup responses.

  1. Press Win + R, type ncpa.cpl, and press Enter to open Network Connections.
  2. Right-click your active connection (Wi-Fi or Ethernet) and choose Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Select Use the following DNS server addresses:
    • Preferred DNS server (Cloudflare): 1.1.1.1 (or Google: 8.8.8.8)
    • Alternate DNS server: 1.0.0.1 (or Google: 8.8.4.4)
  5. Tick Validate settings upon exit and click OK.

Method 4: Toggle DNS over HTTPS (Secure DNS) in Chrome

If encrypted DoH queries are blocked by your local network router or firewall, toggling Secure DNS restores connectivity.

  1. In Chrome, click the three dots > Settings.
  2. Select Privacy and security > Security.
  3. Scroll down to Use secure DNS.
  4. If enabled with a custom provider, switch it to With your current service provider or temporarily toggle it Off to test whether the DoH endpoint was timing out.
  5. Reload your page.

Method 5: Power Cycle Your Wi-Fi Router

Home routers run embedded DNS caching forwarders (dnsmasq) that can lock up when handling high volumes of UDP queries.

  1. Unplug the power cable from your Wi-Fi router and modem.
  2. Wait 30 seconds to allow internal capacitors to fully discharge.
  3. Plug the power cable back in and wait 2 minutes for the DSL/Fiber connection to synchronize.
  4. Test loading the domain in Chrome.

Chrome DNS Error Diagnostic Matrix

Error Message Network Layer Stage Primary Fix
ERR_NAME_NOT_RESOLVED Domain lookup failed before TCP connection Flush Chrome host cache (chrome://net-internals/#dns) & OS DNS
DNS_PROBE_FINISHED_NXDOMAIN DNS server confirmed domain does not exist Verify URL spelling; check domain WHOIS registration
DNS_PROBE_FINISHED_NO_INTERNET Local gateway disconnected from external WAN Reboot Wi-Fi router; check modem internet signal LED
ERR_CONNECTION_TIMED_OUT DNS succeeded, but web server dropped TCP packets Check server firewall status or test via VPN

Frequently Asked Questions

Why does ERR_NAME_NOT_RESOLVED affect only one specific website?

If other websites load smoothly, the problem is usually isolated to that specific domain’s nameservers. The website owner may have updated their DNS records (which takes up to 24–48 hours to propagate worldwide) or failed to renew their domain registration.

Can disabling Chrome extensions fix DNS resolution errors?

Yes. VPN extensions and proxy add-ons (like Hola or NordVPN extensions) alter the browser’s DNS resolution path. If the proxy server goes offline, Chrome will return ERR_NAME_NOT_RESOLVED for all outgoing requests until the extension is disabled.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.