Attempting to open an online service, banking portal, or web page in Google Chrome only to be stopped by the error screen reading “This site can’t be reached. Check if there is a typo in the address. DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED” brings web browsing to an abrupt halt. When you type a domain name into Chrome’s Omnibox, your system’s DNS client must resolve that human-readable domain into a machine-routable IPv4 or IPv6 address. The ERR_NAME_NOT_RESOLVED error signifies that your browser, local operating system DNS cache, or upstream DNS nameservers failed to locate a corresponding DNS record for the host. Whether triggered by stale browser socket pools, corrupt DNS resolver caches, misconfigured proxy profiles, or DNSSEC validation drops, this in-depth guide explains how Chrome handles domain resolution and details proven methods to restore immediate connectivity.
What Triggers ERR_NAME_NOT_RESOLVED in Chrome?
Domain name resolution involves multiple hierarchical caches. Breakdowns commonly occur due to:
- Stale Chrome Internal Host Resolver Cache: Google Chrome maintains its own internal DNS cache and socket pool independent of the host operating system. Stale records cause failed lookups.
- Corrupted Operating System DNS Resolver Cache: Damaged entries in the Windows, macOS, or Linux DNS client cache returning negative resolution responses (NXDOMAIN).
- Unresponsive ISP DNS Nameservers: Your internet service provider’s default recursive DNS servers timing out or failing to resolve specific authoritative root zones.
- Interfering VPNs or Web Proxies: Third-party VPN tunnels or local HTTP proxies misdirecting DNS requests or leaking unresolved queries.
- DNS over HTTPS (DoH) Misconfigurations: Secure DNS settings inside Chrome attempting to route through an unreachable DoH endpoint.
Method 1: Flush Chrome’s Internal Host and Socket Cache
Chrome caches domain-to-IP resolutions directly in browser memory to accelerate page loads. Purging this cache forces a clean network lookup.
- Open a new tab in Google Chrome.
- Type the following URL into the Omnibox and press Enter:
chrome://net-internals/#dns - Locate the Host resolver cache section and click the Clear host cache button.
- Next, navigate to the sockets panel by entering:
chrome://net-internals/#sockets - Click Close idle sockets, then click Flush socket pools.
- Restart Chrome and attempt to reload the website.
Method 2: Flush the Operating System DNS Resolver Cache
Clearing stale DNS mappings stored by your operating system’s networking subsystem ensures your PC requests fresh IP data.
On Windows 11 / 10:
- Press Windows Key + X and select Terminal (Admin) or Command Prompt (Admin).
- Run the following DNS flush command:
ipconfig /flushdns - Reset the Winsock catalog and IP stack:
netsh winsock reset netsh int ip reset - Restart your computer.
On macOS:
- Open Terminal via Spotlight or Applications > Utilities.
- Execute the native directory service cache flush command:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Enter your administrator password when prompted.
Method 3: Switch to Reliable Public DNS Resolvers
If your internet service provider’s DNS infrastructure is experiencing packet drops or routing failures, switching to enterprise-grade public resolvers restores instant resolution.
- On Windows: Press Windows Key + R, type
ncpa.cpl, and press Enter to open Network Connections. - Right-click your active network adapter (Wi-Fi or Ethernet) and select Properties.
- Double-click Internet Protocol Version 4 (TCP/IPv4).
- Select Use the following DNS server addresses and enter:
- Google Public DNS: Preferred:
8.8.8.8| Alternate:8.8.4.4 - Cloudflare DNS: Preferred:
1.1.1.1| Alternate:1.0.0.1
- Google Public DNS: Preferred:
- Check Validate settings upon exit and click OK.
Method 4: Configure Secure DNS (DNS over HTTPS) in Chrome
Configuring encrypted DNS inside Chrome circumvents local ISP filtering and transparent DNS proxies.
- In Google Chrome, click the three vertical dots in the upper-right corner and select Settings.
- Click Privacy and security in the left navigation sidebar, then select Security.
- Scroll down to the Advanced section to find Use secure DNS.
- Toggle the switch On.
- Select With: and choose Google (Public DNS) or Cloudflare (1.1.1.1) from the dropdown menu.
- Relaunch Chrome to test the connection.
Method 5: Disable Web Proxies and Reset Network Adapters
Unintended proxy configurations frequently reroute domain resolution to non-existent gateway ports.
- Press Windows Key + I to open Settings.
- Navigate to Network & internet > Proxy.
- Under Automatic proxy setup, ensure Automatically detect settings is enabled and Use setup script is turned off.
- Under Manual proxy setup, ensure Use a proxy server is turned Off.
- If the issue continues across all websites, return to Network & internet > Advanced network settings > Network reset and click Reset now.