Home > Empowering Tips > ERR_NAME_NOT_RESOLVED in Your Browser
Have you ever encountered this? You type in a website address, press Enter, and instead of loading the page, your browser displays:
ERR_NAME_NOT_RESOLVED
It can be frustrating, especially when you need quick access to a website or email portal. The good news is that this error usually indicates a domain name resolution issue, and in many cases, it can be resolved with a few simple checks.
What Does ERR_NAME_NOT_RESOLVED Mean?
When you visit a website like: www.example.com
Your browser does not directly understand names. It needs to find the website’s numeric IP address, such as: 192.0.2.1
To do this, it asks a DNS server to translate the domain name into the correct IP address.
If that lookup fails, the web browsers may display:
ERR_NAME_NOT_RESOLVED
In simple terms:
Your browser knows the website name, but it cannot find where that website is located.
Common Causes of ERR_NAME_NOT_RESOLVED
There is not just one possible cause. The issue may come from your device, your internet connection, the website’s DNS settings, or the domain name itself.
Below are the most common reasons.
1. The Website Address Was Entered Incorrectly
A simple spelling mistake is one of the most common reasons.
For example, entering “mycomapny.com” instead of “mycompany.com” can lead to an error because the browser is trying to locate the wrong domain.
What to Do:
Carefully review the website address and check for:
- Misspelled words
- Missing extensions such as .com or .my
- Extra spaces or symbols
Even a small typo can prevent the browser from finding the correct site.
2. The DNS Server on Your Network Is Not Responding Properly
Your device usually relies on DNS servers provided automatically by your internet provider. If those servers are slow, unavailable, or returning incomplete information, websites may fail to load.
What to Do:
Try restarting your router first. If the issue continues, consider switching to a public DNS provider such as:
- Google DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare DNS: 1.1.1.1
This often improves DNS reliability.
3. The Domain Name Has Expired
Every domain name must be renewed periodically. If the renewal was missed, the domain may stop resolving correctly.
What to Do:
If you own the domain:
- Check your renewal status
- Review billing notices
- Renew the domain if needed
If you are only visiting the website, you may need to contact the owner.
4. DNS Records Were Changed Incorrectly
DNS records tell visitors where the website and email services are hosted. If those records are missing or incorrect, the domain may stop working.
This often happens after moving to new hosting or changing DNS providers.
For example:
- The A record points to the wrong server IP
- The www record was deleted
- Nameservers still point to an old provider
What to Do: Website owners should review their DNS control panel and confirm that records are correct.
5. DNS Changes Are Still Updating Worldwide
When nameservers or DNS records are changed, those updates do not appear instantly everywhere. Some networks may still use older cached information for a period of time.
For example, the website may load on mobile data but not on office Wi-Fi.
What to Do:
Wait for the update to complete. DNS propagation may take:
- A few minutes
- Several hours
- In some cases, up to 48 hours
6. Your Device Has Old DNS Cache Stored
Your computer or browser may remember older DNS information. If that stored data is outdated, it can interfere with new lookups.
What to Do: Restart the device or clear the DNS cache.
7. Router or Local Network Issues
Sometimes the router itself is the cause. It may hold outdated DNS responses or experience temporary connection problems.
If every device on the same Wi-Fi shows the error, but mobile data works, the local network is worth checking.
What to Do: Turn the router off for about 20 seconds, then restart it.
8. VPN or Security Software Is Interfering
Some VPN applications, firewalls, or antivirus programs route DNS traffic through their own systems. If that service is having trouble, websites may fail to resolve.
What to Do: Temporarily disconnect the VPN or pause the security tool briefly for testing. If the site loads normally afterwards, review that software’s DNS settings.
Step-by-Step Fixes for Visitors
If you are trying to access a website, these are good first steps:
1. Recheck the Website Address: Typos are more common than expected.
2. Refresh the Page: Temporary DNS interruptions sometimes clear quickly.
3. Restart Router and Device: This refreshes your connection.
4. Clear DNS Cache: Useful when one device has the problem but others do not.
5. Change DNS Provider: Switch to Google DNS or Cloudflare DNS.
6. Try Another Network: Use mobile data or another Wi-Fi connection.
7. Disable VPN Temporarily: Useful if the issue began after enabling one.
Additional Checks for Website Owners
If this is your own website, also review the following:
- Domain Status: Ensure the domain is active and paid.
- Nameservers: Confirm they point to the correct DNS provider.
- DNS Records: Check A records, CNAME records, and www entries.
- Recent Changes: If you recently moved hosting or edited DNS, propagation may still be in progress.
- Hosting Provider Support: Your hosting provider can often confirm whether DNS records are correct.
Final Thoughts
ERR_NAME_NOT_RESOLVED usually means the browser cannot match the website name to the correct server address.
Although the message looks technical, the cause is often straightforward: a typo, DNS issue, expired domain, incorrect records, or outdated cache.
Begin with the simple checks first. In many cases, a restart, DNS refresh, or correction to the domain settings is all that is needed.
Frequently Asked Questions
1. Why does the website work on my phone but not computer?
Your computer may be using outdated DNS cache information, a different DNS server, or a different network configuration. Try clearing your DNS cache, restarting your browser, or testing the website in another browser.
2. Why does it work on mobile data but not Wi-Fi?
This often indicates an issue with the DNS settings on your router or your internet service provider’s DNS servers. Connecting through a different network can help confirm whether the issue is network-related.
3. Does this mean the website is offline?
Not necessarily. In many cases, the web server is still online, but the domain name cannot be resolved to the correct IP address. This can occur due to DNS issues, domain expiration, or recent DNS changes.
4. Can the browser itself cause this?
Yes. Browser extensions, built-in VPN features, security software, or corrupted browser cache can sometimes interfere with DNS lookups and trigger the ERR_NAME_NOT_RESOLVED error. Testing in a private/incognito window or a different browser may help identify the cause.
5. How long can this problem last?
The duration depends on the underlying cause:
- DNS cache issue: Usually a few minutes after clearing the cache.
- Temporary DNS outage: A few minutes to several hours.
- DNS propagation after changes: Up to 24 – 48 hours.
- Expired domain name: Until the domain is renewed and DNS services are restored.