How to Fix ERR_NAME_NOT_RESOLVED in Google Chrome: 2026 Sysadmin & User Guide

When browsing the web in Google Chrome, few errors are as common or as ambiguous as ERR_NAME_NOT_RESOLVED.

Unlike 404 Not Found (which proves your browser successfully reached the hosting server) or 500 Internal Server Error (an application crash), ERR_NAME_NOT_RESOLVED means the connection failed before a single packet of web data could be requested. Your browser was completely unable to translate the human-readable domain name (like example.pk) into a machine-routable IPv4 or IPv6 address.

Because DNS operates as a distributed, multi-tiered hierarchy spanning your local PC, office router, Internet Service Provider (ISP), and global authoritative nameservers, the root cause could lie anywhere along that chain.

In this guide, we provide a complete technical breakdown of why ERR_NAME_NOT_RESOLVED occurs, followed by proven troubleshooting steps for both end users and website administrators.

---

1. What Does ERR_NAME_NOT_RESOLVED Mean?

The Domain Name System (DNS) is the phonebook of the global internet. Computers communicate exclusively through numerical IP addresses (such as 195.201.85.14).

When you type a URL into Google Chrome:

[Your Browser]
      │
      ▼ 1. Interrogates OS DNS Cache
[Windows / macOS DNS Client]
      │
      ▼ 2. Queries Recursive Resolver (ISP / 1.1.1.1)
[Recursive DNS Resolver]
      │
      ▼ 3. Queries Root (.) & TLD (.pk / .com)
[Authoritative Nameserver]
      │
      ▼ 4. "No Record Found" or "Query Timed Out"
[Browser Displays: ERR_NAME_NOT_RESOLVED]

When Chrome displays ERR_NAME_NOT_RESOLVED, it means that:

1. The recursive DNS resolver returned an official NXDOMAIN (Non-Existent Domain) response.
2. The DNS lookup timed out because upstream nameservers failed to reply over UDP port 53.
3. A local DNSSEC cryptographic signature verification failed, causing your operating system to discard the lookup result.
4. Local socket or network stack corruption prevented Chrome from communicating with your gateway.

---

2. Part 1: How to Fix ERR_NAME_NOT_RESOLVED as a User

If you are trying to access a website that works fine on your mobile phone’s 4G connection but throws ERR_NAME_NOT_RESOLVED on your home or office computer, follow these client-side fixes:

Fix 1: Flush Google Chrome’s Internal DNS Host Cache

Google Chrome maintains its own internal DNS cache separate from the operating system to accelerate page rendering. Stale entries in this cache frequently trigger false resolution errors:

1. Open Chrome and paste the following into the address bar:

   chrome://net-internals/#dns

2. Click the button labeled “Clear host cache”.
3. Next, navigate to:

   chrome://net-internals/#sockets

4. Click “Close idle sockets” and “Flush socket pools”.
5. Restart your browser and reload the page.

Fix 2: Flush Windows DNS & Reset the Winsock Catalog

A corrupted local DNS cache or damaged Winsock TCP/IP interface in Windows will block DNS lookups across all applications.

Open PowerShell or Command Prompt as Administrator and run:

# Flush local DNS client cache
ipconfig /flushdns

# Release current IP address
ipconfig /release

# Renew IP from DHCP server
ipconfig /renew

# Reset Windows Sockets API
netsh winsock reset

# Reset TCP/IP stack to clean factory defaults
netsh int ip reset

Restart your computer immediately after running these commands to finalize the network reset.

Fix 3: Switch from Unreliable ISP DNS to Anycast Resolvers

Many local Internet Service Providers in Pakistan (including PTCL, Nayatel, and StormFiber) experience intermittent cache synchronization failures or apply aggressive DNS filtering. Switching your primary DNS to globally distributed Anycast resolvers permanently eliminates ISP resolution bottlenecks.

Top Anycast DNS Servers:

• Cloudflare DNS: 1.1.1.1 (Primary) and 1.0.0.1 (Secondary)
• Google Public DNS: 8.8.8.8 (Primary) and 8.8.4.4 (Secondary)

How to Configure in Windows 11:

1. Open Settings (Win + I) > Network & internet > click your active connection.
2. Next to DNS server assignment, click Edit.
3. Choose Manual, switch IPv4 to ON.
4. Set Preferred DNS to 1.1.1.1 and Alternate DNS to 8.8.8.8.
5. Click Save.

Fix 4: Disable Conflicting VPNs and Third-Party Antivirus Shields

Third-party security suites (such as Norton, McAfee, or Avast) and browser VPN extensions often inject local proxy drivers into your network stack. If the VPN tunnel disconnects uncleanly, the local proxy remains bound, causing all subsequent DNS queries to fail with ERR_NAME_NOT_RESOLVED. Temporarily disable VPN extensions and test the connection.

---

3. Part 2: How to Fix ERR_NAME_NOT_RESOLVED as a Website Owner

If multiple visitors or clients are reporting that your business website is throwing ERR_NAME_NOT_RESOLVED, the fault lies within your domain registrar or hosting DNS zone.

Step 1: Verify Authoritative Nameserver Delegation with dig

Check whether your domain’s registrar is correctly pointing to active nameservers:

dig +trace yourdomain.pk

Look at the bottom section of the output:

• Are the nameservers returned correct (e.g., ns1.nextgen.pk and ns2.nextgen.pk)?
• If the output returns SERVFAIL or an empty delegation, log into your domain registrar portal and verify that your nameserver glue records are saved without typographical errors.

Step 2: Confirm the Existence of the DNS “A” Record

The most common mistake webmasters make after migrating to a new VPS or hosting provider is forgetting to recreate the primary A Record:

dig A yourdomain.pk +short
dig A www.yourdomain.pk +short

If both commands return nothing, your domain is essentially an unmapped address in global DNS:

1. Log into your DNS management portal (cPanel Zone Editor or Cloudflare).
2. Add an A record: Host @ pointing to your server’s public IPv4 address.
3. Add a CNAME record: Host www pointing to @.

Step 3: Check for Broken DNSSEC Signatures

If your domain previously had DNSSEC (Domain Name System Security Extensions) enabled at your old host, and you migrated nameservers without updating the DS records at your registrar:

Every DNSSEC-validating resolver (Google, Cloudflare, Quad9) will reject the DNS lookup because the cryptographic cryptographic signature does not match the public key in the TLD zone, throwing an immediate ERR_NAME_NOT_RESOLVED.

The Fix:

1. Check DNSSEC status using dig +dnssec yourdomain.com.
2. If validation fails, log into your domain registrar and delete old DS records, or re-sign the zone with your new DNS provider’s keys.

Step 4: Account for Propagation Windows

If you updated DNS records recently, recursive resolvers honor the previous record’s TTL (Time to Live):

• Standard TTL is usually 3600 seconds (1 hour) to 86400 seconds (24 hours).
• Country-code TLDs like .pk require updates to PKNIC root servers, which can take 4 to 12 hours to synchronize across domestic ISPs.

---

Summary Troubleshooting Checklist

Observation	Probable Cause	Action
Only one PC shows error; works on phone 4G	Local Windows DNS or Chrome cache corruption	Flush Chrome DNS (chrome://net-internals/#dns) and run ipconfig /flushdns.
Site fails across an entire office network	Office router DNS cache locked or ISP resolver failure	Reboot router; change router DNS to 1.1.1.1 and 8.8.8.8.
Global failure (tested on whatsmydns.net)	Missing DNS “A” record or expired domain	Check registrar WHOIS status; add missing A record in cPanel/Cloudflare.
Fails only on resolvers with DNSSEC enabled	Stale DS records at domain registrar	Delete old DS records at your registrar after changing hosting providers.

---

High-Availability DNS Built on Enterprise Infrastructure

A domain is only as dependable as the nameserver cluster answering its queries. Budget hosting companies run DNS resolvers on the same shared nodes that host dynamic PHP websites. When an adjacent user triggers a CPU spike, DNS daemons lag, causing intermittent ERR_NAME_NOT_RESOLVED errors for your visitors.

For mission-critical production platforms:

• Anycast DNS Redundancy: Pair resilient global Anycast nameserver networks with dedicated computing by deploying on bare-metal Dedicated Servers.
• Ultra-Fast Domestic Resolution: For Pakistani banks, corporate portals, and e-commerce stores, hosting on domestic Dedicated Servers in Pakistan ensures your DNS queries and web traffic route through local PKIX fiber, eliminating latency and packet drops across international undersea cables.

---