You are likely here because you have already cleared your browser cache, flushed your DNS, and restarted your router. And you are still staring at an ERR_NAME_NOT_RESOLVED screen.
If the basic fixes failed, you are not dealing with a temporary cache glitch. You are dealing with a conflict in your operating system’s TCP/IP stack, a rogue entry in your local hosts file, or a “Secure DNS” collision.
This guide skips the basics. We assume you have already tried ipconfig /flushdns. Here is how to fix ERR_NAME_NOT_RESOLVED when the standard advice fails.
What ERR_NAME_NOT_RESOLVED Means
DNS converts a domain name into a server IP address. Without DNS, your browser cannot find the website.
Here is the simple flow:
Browser → DNS → IP address → Server → Website loads
If DNS fails at any point, the browser shows ERR_NAME_NOT_RESOLVED. This is a critical barrier for site owners because if users can’t resolve your address, they can’t see the value of your platform. When considering why choose WordPress, its robust community support for troubleshooting such connectivity issues is a major factor.
This means one of these is true:
| Cause | What it means | Impact |
|---|---|---|
| Missing DNS record | Domain has no IP assigned | Website cannot load |
| Incorrect DNS record | DNS points to wrong server | Connection fails |
| DNS not propagated | DNS update still spreading | Temporary downtime |
| Expired domain | DNS stopped working | Website completely offline |
The important point is this. The server may still be running. But DNS cannot locate it. Until DNS resolves correctly, the website stays inaccessible.
Identify Whether the Problem Is on Your Device or Website
This is the most important step. Most people skip it and waste hours fixing the wrong thing.
Follow this simple diagnostic process.
Step 1. Open the website on mobile data
Turn off WiFi. Use mobile internet. If it works on mobile but not on your desktop, the issue is local.
Many modern administrators avoid these desktop-specific hurdles by introducing the New User Approve mobile app to manage their site registrations on the go via a cellular connection.
| Result | Meaning | Action |
|---|---|---|
| Website loads | Your device or WiFi DNS is broken | Fix your local DNS |
| Website fails | Website DNS is broken | Fix domain DNS |
This instantly narrows the root cause.
Step 2. Test using another device
Open the same website on:
- another phone
- another laptop
- another network
If it fails everywhere, the issue is on the website side. If it works elsewhere, your device is the problem.
Step 3. Check global DNS propagation
Use a DNS checker tool. Enter your domain.
| Result | Meaning |
|---|---|
| No IP returned | DNS records missing |
| Different IP globally | DNS propagation incomplete |
| Correct IP everywhere | Local DNS problem |
This step removes guesswork and it tells you exactly where to fix the issue.
Fix ERR_NAME_NOT_RESOLVED (Visitor-Side Fixes)
If the website works on other networks but not yours, the problem is your local DNS. Use this checklist. These fixes solve most cases in minutes.
Fix 1. Clear DNS cache
Your device stores old DNS records. If they are outdated, the browser cannot find the correct server.
Clear the cache to force a fresh DNS lookup.
Windows
ipconfig /flushdns
Mac
sudo dscacheutil -flushcache
After this, restart your browser and test again.
Fix 2. Change DNS server
Your ISP DNS is often slow or unreliable. Switching to a trusted DNS provider fixes resolution failures.
Use one of these:
| Provider | Primary DNS | Secondary DNS |
|---|---|---|
| Google Public DNS | 8.8.8.8 | 8.8.4.4 |
| Cloudflare DNS | 1.1.1.1 | 1.0.0.1 |
Cloudflare DNS is faster and more reliable in most regions.
Fix 3. Restart your router
Routers cache DNS records. And sometimes they store broken entries. Restarting the router forces it to refresh DNS.
Steps:
- Turn off the router
- Wait 30 seconds
- Turn it back on
This clears router-level DNS errors.
Fix 4. Disable VPN temporarily
VPN services override DNS routing. And many VPN DNS servers fail to resolve domains correctly. Turn off VPN. Then reload the website.
If the site loads, your VPN is the cause. Switch VPN provider or use public DNS instead.
Fix ERR_NAME_NOT_RESOLVED (Website Owner Fixes)
If your website fails on all devices and networks, your DNS is broken. This blocks users, search engines, and revenue. Fix these in order.
Fix 1. Check DNS records
Your domain must point to the correct server IP. Verify these records in your DNS panel:
| Record | What to check | Example |
|---|---|---|
| A record | Must exist and point to server IP | example.com → 192.168.1.1 |
| CNAME | Must point to correct domain | www → example.com |
| Missing records | Domain cannot resolve | Website fails |
If the IP is wrong or missing, DNS resolution fails instantly. You can get the correct IP from your hosting dashboard.
Fix 2. Check nameservers
Nameservers control where DNS records are managed. If nameservers point to the wrong provider, DNS breaks.
Your domain must use nameservers from either:
- your hosting provider
- or Cloudflare
Check nameservers in your domain registrar panel.
| Correct setup | Result |
|---|---|
| Nameservers match DNS provider | DNS resolves |
| Nameservers mismatch | ERR_NAME_NOT_RESOLVED |
This is one of the most common causes after migrations.
Fix 3. Check DNS propagation
After changing DNS records, propagation takes time. Typical propagation time:
| Change type | Time |
|---|---|
| Minor change | 5–30 minutes |
| Nameserver change | 1–24 hours |
| Global propagation | Up to 48 hours |
Use a DNS checker tool. If no IP appears globally, DNS is not propagated or misconfigured.
Fix 4. Check domain expiration
Expired domains stop resolving completely. Check the domain status in your registrar.
| Status | Result |
|---|---|
| Active | DNS works |
| Expired | DNS stops |
| Suspended | Website offline |
Renewing the domain restores DNS.
Fix 5. Check hosting server status
If your hosting server IP changes, DNS still points to the old server. This causes resolution failure.
Check your hosting dashboard and confirm:
- server is active
- IP address matches DNS A record
Update DNS if IP changed.
Fix ERR_NAME_NOT_RESOLVED in Cloudflare
Cloudflare sits between your domain and server. If misconfigured, DNS resolution fails.
Common Cloudflare causes:
| Cause | Result |
|---|---|
| Missing A record | Domain cannot resolve |
| Incorrect nameservers | Cloudflare not active |
| Proxy enabled incorrectly | DNS conflict |
Follow this checklist.
Step 1. Verify DNS records in Cloudflare
Login to Cloudflare DNS panel.
Confirm:
- A record exists
- IP matches your server
- Domain and www both configured
Missing records cause instant failure.
Step 2. Verify nameservers point to Cloudflare
Check nameservers in your domain registrar. They must match Cloudflare nameservers exactly.
If not, Cloudflare cannot resolve DNS.
Step 3. Disable proxy temporarily
Cloudflare proxy can block resolution if origin server is unreachable.
In DNS panel:
- Turn off proxy (orange cloud → grey cloud)
- Wait 1 minute
- Test website
If the website loads, the origin server connection is the issue.
Fix ERR_NAME_NOT_RESOLVED in WordPress
This error is common after WordPress migration or hosting changes. If you are using a site with many contributors, ensure you understand what is a user role in WordPress so that only authorized admins are making these sensitive DNS and hosting changes.
Most common causes:
| Cause | What happens | Result |
|---|---|---|
| Hosting migration | DNS still points to old server | Site unreachable |
| Domain change | DNS not updated | Resolution fails |
| Incorrect A record | Domain points to wrong IP | Connection fails |
Follow these fixes.
Step 1. Update DNS A record
Go to your DNS provider. Make sure the A record points to your current hosting server IP. You can find this IP in your hosting dashboard.
Step 2. Verify domain in hosting panel
Login to your WordPress hosting panel. Confirm your domain is added and active. If the domain is missing, the server cannot respond.
Once DNS and hosting match, the error resolves.
What are The Tools to Diagnose DNS Issues?
These tools show exactly where DNS fails.
Tool 1. nslookup
This checks if your domain resolves to an IP.
Example:
nslookup example.com
| Result | Meaning |
|---|---|
| IP address returned | DNS working |
| No IP returned | DNS broken |
This is the fastest way to confirm DNS resolution.
Tool 2. dig
This shows detailed DNS information, including authoritative nameservers.
Example:
dig example.com
It helps identify:
- wrong DNS provider
- missing DNS records
- propagation issues
Developers and hosting teams rely on this tool.
Tool 3. DNS propagation checker
This shows DNS status globally. It confirms whether DNS works across regions.
| Result | Meaning |
|---|---|
| IP visible globally | DNS working |
| Missing in regions | Propagation incomplete |
| Missing everywhere | DNS misconfigured |
This tool confirms whether the issue is local or global.
Prevent ERR_NAME_NOT_RESOLVED Errors
Weak DNS infrastructure leads to ranking loss and traffic drops. You can prevent most DNS resolution errors by controlling your DNS setup. Prevention is easier than recovery, especially if your site generates leads or revenue.
Follow these best practices:
| Prevention step | Why it matters |
|---|---|
| Use a reliable DNS provider like Cloudflare | Faster and stable DNS resolution |
| Avoid frequent DNS changes | Reduces propagation errors |
| Monitor domain expiration | Prevents sudden DNS failure |
| Keep DNS records documented | Helps fix issues quickly |
Reliable DNS providers reduce downtime risk. And stable DNS improves uptime, SEO crawling, and user access.
ERR_NAME_NOT_RESOLVED vs Other DNS Errors
Not all DNS errors mean the same thing. Each error points to a different failure point.
| Error | Meaning | Root cause |
|---|---|---|
| ERR_NAME_NOT_RESOLVED | DNS cannot find IP address | Missing or incorrect DNS record |
| DNS_PROBE_FINISHED_NXDOMAIN | Domain does not exist | Domain not registered or expired |
| ERR_CONNECTION_REFUSED | Server rejected connection | Server offline or blocked |
Last Word
ERR_NAME_NOT_RESOLVED always means DNS failed to resolve your domain. The fix depends on the root cause. It may be your device, DNS records, nameservers, or hosting configuration. Most fixes take minutes if you check DNS records and nameservers first. Fixing DNS restores access, traffic, and search visibility.
