ERR_NAME_NOT_RESOLVED: Causes and Fixes for Visitors and Owners

ERR_NAME_NOT_RESOLVED is Chrome's message when your device could not turn the hostname into an IP address. The page reads "This site can't be reached" with "server IP address could not be found." Firefox says "Hmm. We're having trouble finding that site," Safari says "Safari Can't Find the Server," and Edge says "Hmm... can't reach this page."

It is a lookup failure that happens before any connection exists. It is a broader label than DNS_PROBE_FINISHED_NXDOMAIN, which Chrome shows when its diagnostic probe confirms the resolver answered "this name does not exist." ERR_NAME_NOT_RESOLVED can also mean the resolver timed out, returned an error such as SERVFAIL, or was never reachable.

Narrow it down in one minute

dig example.com A +short
dig example.com A @1.1.1.1 +short
dig example.com A @8.8.8.8 +short

Interpret the three results:

• All empty or NXDOMAIN: the name does not resolve anywhere. The problem is the domain's DNS or the name itself.
• Your default resolver fails but 1.1.1.1 and 8.8.8.8 work: your local resolver (router, ISP or office DNS) is the problem.
• All three work but the browser fails: the problem is local to the browser or device: cache, hosts file, VPN, extension or proxy.

If you do not have dig, use nslookup example.com on Windows. The DNS चेकर queries from several public resolvers at once.

If you are a visitor

1. Check for typos. Missing letters and wrong TLDs are the top cause.
2. Test another site. If nothing loads, see DNS_PROBE_FINISHED_NO_INTERNET instead.
3. Flush the OS cache with the commands below, then continue with step 4.

# Windows (Administrator prompt)
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
# Linux with systemd-resolved
resolvectl flush-caches

Next:

1. Clear Chrome's own cache. Visit chrome://net-internals/#dns and click Clear host cache. Then restart the browser.
2. Switch DNS servers. Set the adapter's DNS to a public resolver such as 1.1.1.1 or 8.8.8.8, or your provider's alternative, and retry.
3. Check the hosts file. An entry mapping the name to a dead address, or a blocklist, overrides DNS. It lives at C:\Windows\System32\drivers\etc\hosts on Windows and /etc/hosts on macOS and Linux.
4. Turn off VPNs and secure-DNS settings temporarily. Chrome's "Use secure DNS" option (Settings, Privacy and security, Security) can fail with certain resolvers; try setting it to your current provider or off to test.
5. Restart the router. Some home routers run a faulty DNS forwarder that drops queries after long uptime.

If you own the site

When the name fails from everywhere, treat it as a DNS incident.

Records missing or deleted

Confirm the A or AAAA (or CNAME) record exists at the authoritative servers, not just in your control panel's draft state:

dig +short NS example.com
dig example.com A @ns1.your-dns-provider.com

A status: NOERROR with no answer means no record of that type. A status: NXDOMAIN means no such name. Create or correct the record.

Delegation is broken

If the registrar points to nameservers that do not host your zone, or to servers that are down, lookups fail. Compare the NS records at the registry with those in the zone using the नेमसर्वर लुकअप. A mismatch after a provider change is common; see how to change nameservers without downtime.

Domain expired or suspended

Registrars stop delegating an expired domain and registries may place it on hold. Check status codes in the WHOIS लुकअप. Terms like clientHold or serverHold explain a sudden global failure. Recovery is covered in the expiry grace and redemption guide.

DNSSEC validation failures

A broken DNSSEC chain makes validating resolvers return SERVFAIL, so users on those resolvers see a failure while others do not. This often follows a DNS provider move that kept the old DS record. Check with the DNSSEC चेकर and read DNSSEC explained.

Propagation and caching

A newly created record may not be visible everywhere at once, and a negative answer (no such name) can be cached for the zone's negative TTL. See how long DNS propagation takes. Lowering TTLs before planned changes helps; read TTL explained.

Check what changed

If the site worked yesterday, compare records over time with DNS इतिहास to spot a deleted or altered record.

Confirm the fix

1. Query several public resolvers with the DNS चेकर; all should return the same expected records.
2. Run the वेबसाइट हेल्थ चेक to check DNS, TLS and HTTP in one pass.
3. Add an uptime monitor with DNS-change alerts so a vanished record does not go unnoticed.

अगले कदम

• Learn the basics in DNS explained for website owners.
• If the resolver returns "no such domain," see DNS_PROBE_FINISHED_NXDOMAIN.
• If the name resolves but the connection fails, see This site can't be reached.
• Check whether the problem is only yours with website down for everyone or just me.

सामान्य प्रश्न

Is ERR_NAME_NOT_RESOLVED the same as NXDOMAIN?

Not exactly. NXDOMAIN is one specific DNS answer meaning the name does not exist. ERR_NAME_NOT_RESOLVED covers that plus timeouts and other failures.

Why does it happen after I change DNS records?

Resolvers may still hold the old or negative answer until its TTL expires. Flush your local cache and test against a public resolver to see the current state.

Why do some people see it and others do not?

Different resolvers, different caches or a DNSSEC problem that only validating resolvers enforce. Test from several places.

Can an antivirus or VPN cause it?

Yes. Both may hijack DNS. If switching them off fixes it, update the software or change its DNS settings.

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.