Severity: Critical · Fix time: 5–15 min · Skill level: Beginner

ERR_NAME_NOT_RESOLVED is a Chrome browser error that appears when the browser cannot resolve a domain name to an IP address — meaning the DNS lookup failed before any connection to the web server was even attempted. Chrome displays it as: “This site can’t be reached. [domain]’s server IP address could not be found. ERR_NAME_NOT_RESOLVED.” No web page loads; the browser simply cannot find out where to send the request.

This error differs from its close sibling, DNS_PROBE_FINISHED_NXDOMAIN, in an important way: ERR_NAME_NOT_RESOLVED is the general Chrome error for any DNS resolution failure, covering scenarios where the lookup couldn’t complete for any reason — no network, DNS server unreachable, stale cached record, or domain not found. DNS_PROBE_FINISHED_NXDOMAIN specifically means the DNS probe completed and definitively found that the domain does not exist. ERR_NAME_NOT_RESOLVED is broader; NXDOMAIN is a specific subset confirming non-existence. An expired domain registration causes both errors; a device with no internet connection causes only ERR_NAME_NOT_RESOLVED.

Need a quick map of every WordPress error? See our 70+ WordPress Errors Guide → for a categorized reference of every common WordPress issue.

[Image: Chrome browser showing ERR_NAME_NOT_RESOLVED error page with “This site can’t be reached” heading and DNS-related message]

How DNS Resolution Works — And Why It Fails

When you type a domain into Chrome, the browser asks a DNS resolver — your ISP’s DNS server or a third-party service like Google (8.8.8.8) — to look up the IP address for that domain. The resolver checks its cache, then queries the DNS hierarchy if needed. ERR_NAME_NOT_RESOLVED appears when this process fails to return a valid IP for any reason:

  • No internet connection — The device can’t reach any DNS server. Test by navigating to a known-working site like google.com.
  • Stale DNS cache — The device or Chrome has cached an old DNS record that no longer resolves. Common after a domain migrates to a new server, a CDN is added, or DNS records change.
  • Domain not yet propagated — DNS changes take time to propagate globally (minutes to 48 hours depending on TTL). Some devices see the new record; others still see the old one or nothing.
  • Domain registration expired — If the domain registration lapses, the registrar removes DNS records from circulation. The domain ceases to exist at the DNS level for all visitors.
  • Incorrect DNS configuration — Misconfigured nameservers, missing A records, or incorrect settings after a server migration produce a domain that exists in the registry but has no resolvable IP.
  • ISP DNS filtering or outage — Your ISP’s DNS servers may be down, or a content filter may be blocking the lookup for this domain.

Check This First — 2-Minute Diagnostic

  1. Try another site — Navigate to google.com. If that also fails with ERR_NAME_NOT_RESOLVED, the problem is your network or DNS — not the WordPress site.
  2. Try a different browser or device — If the domain loads in Firefox or on a phone using cellular data, the issue is isolated to Chrome on your current machine or network.
  3. Clear Chrome’s DNS cache — Type chrome://net-internals/#dns in the address bar, click “Clear host cache.” Also open chrome://net-internals/#sockets and click “Flush socket pools.” Retry.
  4. Flush your OS DNS cache — Windows: ipconfig /flushdns in an admin Command Prompt. Mac: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Linux: sudo systemd-resolve --flush-caches.
  5. Try the site by IP — If you know the server’s IP (from your hosting control panel), access http://[IP-address] directly. If it loads, DNS records are the problem, not the server.

Purpose & Benefits

1. Distinguishing Device-Side From Domain-Side Causes

ERR_NAME_NOT_RESOLVED is one of the few WordPress-related errors that may have nothing to do with WordPress at all. A stale DNS cache on one device, a local network DNS issue, or a browser-specific problem can cause this error for only one person while everyone else reaches the site normally. Identifying whether the error is device-specific or universal determines the entire diagnostic approach — and avoids unnecessary server-side changes.

2. Preventing Outages During DNS Changes

DNS changes carry a risk of temporary ERR_NAME_NOT_RESOLVED errors during propagation. Reducing the DNS TTL to 300 seconds before planned changes then restoring it afterward shrinks the propagation window from hours to minutes — the single most effective way to reduce visitor impact during a DNS migration.

3. Domain Expiry Is a Business-Critical Risk

An expired domain causes ERR_NAME_NOT_RESOLVED for all visitors worldwide — not one device. Recovery requires re-activating the domain, which can take hours and may involve additional fees if the domain has entered a grace or redemption period. Domain expiry monitoring belongs in the same category as SSL certificate monitoring: automated, with alerts well in advance.

Examples

1. Stale DNS Cache After Server Migration

A WordPress site moves to a new hosting provider. The developer updates the A record. Most visitors see the new site, but users on corporate networks — where IT manages DNS caches — continue seeing ERR_NAME_NOT_RESOLVED for up to 48 hours. Fix for affected users: flush the OS DNS cache (command above) and clear Chrome’s DNS cache via chrome://net-internals/#dns. For faster future migrations, reduce the domain’s TTL to 300 seconds at least 24 hours before migrating, then restore it after.

2. Chrome DNS Cache After Nameserver Change

A site owner updated nameservers two days ago. The change propagated fully — Firefox and mobile devices load the site correctly. But Chrome on their desktop still returns ERR_NAME_NOT_RESOLVED. Chrome maintains its own internal DNS cache independent of the OS. Fix:

1. Type chrome://net-internals/#dns in the Chrome address bar
2. Click "Clear host cache"
3. Open chrome://net-internals/#sockets
4. Click "Flush socket pools"
5. Close Chrome completely, reopen, and retry

No server changes needed. Chrome-specific fix only.

3. Missing A Record After Adding Cloudflare

A business adds Cloudflare and changes the domain’s nameservers. During setup, the A record pointing the domain to the WordPress server’s IP wasn’t added to Cloudflare’s DNS panel — it existed at the old registrar but wasn’t imported. All visitors see ERR_NAME_NOT_RESOLVED. Diagnose and fix:

# Check if the domain resolves to a valid IP
nslookup yourdomain.com 8.8.8.8
# Or:
dig yourdomain.com A

# If the response is NXDOMAIN or returns no address,
# the A record is missing. Log in to Cloudflare DNS panel and add:
# Type: A | Name: @ | Value: [server IP] | Proxy: On (or DNS only for testing)
# Type: A | Name: www | Value: [server IP] | Proxy: On

Common Mistakes to Avoid

  • Assuming the server is down when only DNS is failing — ERR_NAME_NOT_RESOLVED means Chrome couldn’t resolve the domain name, not that the server is offline. Test by accessing the site’s IP address directly before assuming a server problem.
  • Making DNS changes during business hours without preparation — DNS changes affect all visitors globally. Without reducing the TTL first, some visitors may see ERR_NAME_NOT_RESOLVED for hours. Reduce TTL to 300 seconds 24 hours before any planned migration.
  • Confusing ERR_NAME_NOT_RESOLVED with DNS_PROBE_FINISHED_NXDOMAIN — NXDOMAIN definitively means the domain doesn’t exist in DNS (unregistered, expired, or never created). ERR_NAME_NOT_RESOLVED includes NXDOMAIN scenarios but also covers network failures where DNS couldn’t complete at all. The distinction matters for diagnosis.
  • Forgetting to check domain registration expiry — A domain can have valid hosting, a valid SSL certificate, and correct DNS records — but if the registration expired, all of that becomes unreachable. Check domain expiry via WHOIS if a universal ERR_NAME_NOT_RESOLVED appears without recent DNS changes.

Best Practices

1. Monitor Domain Registration Expiry

Enable auto-renew at your domain registrar and set calendar reminders at 60 and 30 days before expiry. An expired domain creates an immediate, site-wide ERR_NAME_NOT_RESOLVED for all visitors. Recovery can take hours. This is one of the most preventable access failures.

2. Reduce TTL Before Planned DNS Changes

Set the domain’s A record TTL to 300 seconds in your DNS provider at least 24 hours before a planned migration. This ensures resolvers expire the old record quickly after the change. With TTL at 300 seconds, propagation takes minutes rather than hours. Restore TTL to 3600 once the migration is confirmed stable.

3. Verify DNS Records After Every Hosting Migration

Before pointing live traffic to a new server, confirm the A record for the apex domain and www subdomain both point to the new IP. Use nslookup yourdomain.com 8.8.8.8 or whatsmydns.net to check global propagation. Catching a missing A record before the nameserver update goes live prevents a full ERR_NAME_NOT_RESOLVED outage.

Frequently Asked Questions

What’s the difference between ERR_NAME_NOT_RESOLVED and DNS_PROBE_FINISHED_NXDOMAIN?

ERR_NAME_NOT_RESOLVED means Chrome’s DNS lookup failed for any reason — no internet, DNS server unreachable, stale cache, or domain not found. DNS_PROBE_FINISHED_NXDOMAIN is a specific subset: the DNS probe completed and returned NXDOMAIN, meaning the domain definitively doesn’t exist at the DNS level. NXDOMAIN typically means the domain isn’t registered, has expired, or has no DNS records configured. See our DNS_PROBE_FINISHED_NXDOMAIN entry for that specific error’s fix paths.

Does ERR_NAME_NOT_RESOLVED mean my WordPress site is down?

Not necessarily. The error means Chrome couldn’t resolve the domain name to an IP address. The WordPress server may be running perfectly. Test from a different browser and device before assuming a server problem. If the error is universal across all devices and browsers, the domain’s DNS configuration or registration is the issue — not the server.

How long do DNS changes take to propagate?

It depends on the TTL of the record being changed. A record with TTL 3600 (one hour) means resolvers can cache the old value for an hour before checking for updates. Globally, propagation can take 24–48 hours in rare cases, though most resolvers update within a few hours. Reduce TTL to 300 seconds before planned migrations to speed this up significantly.

Can a VPN cause ERR_NAME_NOT_RESOLVED?

Yes. VPNs route DNS lookups through their own servers. A misconfigured VPN DNS server or a VPN blocking certain domain categories produces ERR_NAME_NOT_RESOLVED for affected domains. Disable the VPN and test. If the domain loads without it, the issue is the VPN’s DNS configuration.

Related Glossary Terms

How CyberOptik Can Help

Still broken? Our team fixes WordPress errors like this in under 30 minutes for maintenance clients. ERR_NAME_NOT_RESOLVED can stem from a misconfigured DNS zone, an expired domain registration, a failed nameserver update after a hosting migration, or a local cache issue that’s harder to isolate than it looks. We handle DNS configuration, domain migrations, hosting moves, and Cloudflare DNS setup as part of our WordPress maintenance services. Contact us if your site is unreachable.