The err_name_not_resolved error means your browser can't find the website's address, so the page won’t load. This happens when your device fails to translate the website name into its IP address, usually due to DNS problems, network issues, or browser glitches. You can fix it by refreshing the page, clearing your browser cache, restarting your router, changing DNS settings, or checking your system’s hosts file.
What does err_name_not_resolved mean and why am I seeing it?
The err_name_not_resolved error appears when your browser tries to visit a website but can't convert the website's name (like www.example.com) into its numerical IP address. Computers communicate using IP addresses, so this translation—called DNS resolution—is necessary to load a site. If DNS resolution fails, the browser shows this error instead of the page. You'll usually see it immediately after trying to open a site, before any content loads. Without the IP address, your device doesn't know where to send your request, so the page won't appear.
Could my DNS or internet connection be causing err_name_not_resolved?
DNS (Domain Name System) works like the internet's phone book, translating website names into IP addresses. If your DNS server isn't responding or your internet connection is unstable, your device can't look up website names, causing this error. Network problems like a disconnected router, weak Wi-Fi signal, or outages from your internet provider can also disrupt DNS lookups. To check if DNS or your connection is the cause, try visiting a website by its IP address if you know it (which is rare) or try accessing websites from another device on the same network. If other devices also can’t load websites, the problem is likely with your network or DNS, not just your computer or browser.
How can I fix err_name_not_resolved step by step?
- Refresh the webpage. Sometimes the error is temporary. Click your browser’s refresh button or press F5.
- Clear your browser’s cache. Stored data might interfere with loading sites.
- In Chrome, go to Settings > Privacy and security > Clear browsing data > Cached images and files > Clear data.
- Restart your router. Unplug its power, wait 30 seconds, then plug it back in. This often resolves network glitches.
- Flush your computer’s DNS cache. This removes outdated DNS entries that might cause errors.
- On Windows:
ipconfig /flushdns- On Mac:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder- Change your DNS server to a public DNS like Google or Cloudflare.
- On Windows, open Network Connections > Your active network > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Use the following DNS server addresses.
- Enter: - Google DNS: 8.8.8.8 and 8.8.4.4 - or Cloudflare DNS: 1.1.1.1 and 1.0.0.1
- Check your system’s hosts file for incorrect entries that could block websites.
- On Windows, it’s located at C:\Windows\System32\drivers\etc\hosts.
- Open it with a text editor and look for lines containing the website you can’t reach. Delete those lines if found.
- Temporarily disable browser extensions or security software. Sometimes they interfere with DNS lookups.
Try each step one at a time, then test if the website loads before moving to the next.
How do I confirm the err_name_not_resolved error is fixed?
After each fix, open your browser and enter the website address again. If the page loads normally without the error, the problem is solved. You can also try other websites; if they load, your connection and DNS are working.
If you’re comfortable using the command line, run a ping or nslookup command to test DNS resolution:
- On Windows:
nslookup www.example.com- On Mac or Linux:
nslookup www.example.comIf the command returns the website’s IP address, DNS is working. If it shows an error or no address, the issue remains.
What can I do to prevent err_name_not_resolved from happening again?
To reduce the chance of this error recurring, use reliable DNS servers like Google (8.8.8.8) or Cloudflare (1.1.1.1). Keep your router’s firmware updated to improve network stability. Restart your router occasionally to clear temporary glitches. Regularly clear your browser’s cache and keep your browser updated. Avoid installing browser extensions or software that might interfere with network settings unless you trust them. If you experience frequent internet problems, contact your internet service provider to check for ongoing issues.
Before you start
This guide applies to most desktop and laptop computers running Windows, Mac, or Linux, and it requires basic user privileges. Restarting your router and changing DNS settings do not require administrator privileges but editing system files like the hosts file does require administrator or sudo access.
Before starting, confirm that the problem occurs on multiple websites and devices if possible. This helps determine if the issue is local to your device or your network.
No restart of your computer is required to begin troubleshooting, but you may need to restart your browser or router during the process.
Conclusion
If the err_name_not_resolved error continues to block your access, follow the step-by-step fixes starting with the simplest. Check your connection and DNS settings, clear caches, and review system files. If none of these steps work, contact your internet provider or the website’s support for further help. Using trusted DNS servers and keeping your devices updated can help prevent this error in the future.
Frequently Asked Questions
Is err_name_not_resolved caused by my browser?
Not usually. This error mostly happens because your device can’t translate website names into IP addresses due to DNS or network problems, though browser issues can sometimes contribute.
Can I get err_name_not_resolved on my phone?
Yes, mobile devices can show this error if their DNS settings or internet connection have problems, just like computers.
When should I contact my internet provider about this error?
If multiple devices on your network show the error and you’ve already tried basic fixes like restarting your router, it’s a good idea to contact your ISP to check for network or DNS problems.
What if err_name_not_resolved only happens with one website?
That might mean the website’s server is down or misconfigured. You can try again later or contact the website owner for support.