Master Network and DNS troubleshooting and resolve issues with ease!
Get Your Free Guide on How to Fix Common Network and DNS issues
Google reCAPTCHA used. Privacy Policy and Terms of Service apply
ERR_NAME_NOT_RESOLVED Error – 9 Ways to Fix It
Table of Contents
The ERR_NAME_NOT_RESOLVED error is a DNS-related error that prevents your browser from connecting to a website.
It interrupts browsing and can frustrate users who don’t know how to address it. Luckily, it’s usually easy to fix.
This guide outlines nine simple fixes to help you quickly resolve the problem and restore website access.
When this error appears, it means that your browser can’t find the server hosting the website you’re trying to visit.
This can happen for various reasons, such as issues with the DNS server or misconfigured settings on your device.
How to Fix ERR_NAME_NOT_RESOLVED
To fix the ERR_NAME_NOT_RESOLVED error, you need to address the underlying issues that prevent your browser from resolving the website’s domain name.
Here’s a general approach to troubleshooting and fixing the error:
- Check your internet connection – Make sure that your device is properly connected to the internet.
- Restart your router and devices – A restart can resolve temporary network issues.
- Clear browser cache and cookies – Old browsing data can sometimes interfere with DNS resolution.
- Flush DNS cache – Clear your local DNS cache to eliminate outdated or incorrect entries.
- Update or reset DNS settings – Check if your DNS settings are configured properly.
- Temporarily disable firewalls – Security layers can sometimes block DNS resolution.
- Reset browser settings – Ensure your browser is up to date or reset it to its default settings.
- Scan for malware – Malicious software can cause network issues, including DNS failures.
- Check your hosts file – Incorrect entries in your hosts file can prevent DNS resolution.
We’ll walk you through each step in more detail in the sections below.
1. Check your Internet Connection
When you’re encountering the ERR_NAME_NOT_RESOLVED error, the first thing to check is your internet connection. A weak or disconnected network can prevent your browser from accessing websites.
- Verify Wi-Fi or ethernet connection: Check if your device is connected to the network. Try to go to other pages to see if you get similar errors.
- Test with another device: Try accessing a website on a different device using the same network. If you can replicate the issue with different devices, the problem may be with your network.
If your internet connection is stable and the issue persists, move on to the next troubleshooting step.
2. Restart Router and Devices
If the previous steps didn’t resolve the ERR_NAME_NOT_RESOLVED error, try restarting your router and devices. This can help clear any temporary network issues that may be causing the problem.
To restart your router:
- Unplug your router’s power cable.
- Wait for about 30 seconds, then plug it back in.
- Allow the router to fully restart and reconnect to the network.
After restarting, check if the website loads correctly. If the issue persists, move on to the next troubleshooting step.
3. Clear Browser Cache and Cookies
Cached data and cookies can sometimes interfere with DNS resolution by storing outdated or corrupted information.
Clearing your browser’s cache and cookies can resolve the ERR_NAME_NOT_RESOLVED error. The steps to clear cache and cookies vary depending on your browser.
After clearing the data, restart your browser and try visiting the website again.
4. Flush DNS Cache
If clearing browser cache and cookies does not resolve the issue, the next step is to reset the DNS resolver cache on your device.
Flushing your DNS cache can fix the ERR_NAME_NOT_RESOLVED error by clearing out any outdated or corrupted DNS information.
The steps for flushing the DNS cache depend on your device OS. You can find detailed instructions in our dedicated DNS flushing articles for Windows, MacOS and Linux.
After flushing the DNS cache, test the website again. If the issue continues, proceed to the next step.
5. Update or Reset DNS Settings
Incorrect DNS settings can prevent your device from properly resolving domain names.
If flushing the DNS cache didn’t resolve the ERR_NAME_NOT_RESOLVED error, updating your DNS settings might help.
Using Cloudflare (1.1.1.1) or Google DNS (8.8.8.8) instead of your network’s default DNS can offer several benefits.
These third-party DNS providers are generally faster, more reliable, and provide enhanced privacy and security features.
Steps to update or reset DNS settings:
5.1. For Windows
1. Click the Start button > search for and open Control Panel > Network and Internet
2. Click on Network and Sharing Center > Change adapter settings to the left:
3. Right-click your active network connection (Wi-Fi or ethernet) and select Properties
4. Scroll down and double-click on Internet Protocol Version 4 (TCP/IPv4). > Select Use the following DNS server addresses.
5. Enter the public DNS servers:
- Preferred DNS server: 1.1.1.1 (Cloudflare DNS) or 8.8.8.8 (Google DNS)
- Alternate DNS server: 1.0.0.1 (Cloudflare DNS) or 8.8.4.4 (Google DNS)
6. Click OK and restart your device.
5.2. For macOS
1. Click the Apple logo in the upper left > System Settings > Network
2. Select Details for your active connection (Wi-Fi or ethernet).
3. Go to the DNS tab > Click the + button to add a new dns server > Add the following DNS addresses:
- 1.1.1.1 (Cloudflare DNS) or 8.8.8.8 (Google DNS)
- 1.0.0.1 (Cloudflare DNS) or 8.8.4.4 (Google DNS)
4. Click OK.
After updating the DNS settings, restart your device and check if the issue is resolved. If it persists, move on to the next step.
6. Disable Firewalls Temporarily
Sometimes, firewalls can interfere with the resolution of domain names, leading to the ERR_NAME_NOT_RESOLVED error.
Temporarily disabling them can help determine if they are the cause of the issue.
Steps to disable firewall temporarily:
6.1. For Windows
1. Open Windows Firewall:
- Press Windows + R, type firewall.cpl, and press Enter.
- In the left pane, click Turn Windows Defender Firewall on or off.
2. Disable firewall:
- Select Turn off Windows Defender Firewall for both private and public networks.
3. Test the connection: Try accessing the website to see if the error is resolved.
4. Re-enable firewall: Go back to the same settings and turn the firewall back on.
6.2. For macOS
1. Click on the Apple logo > System Settings > Network
2. Click on the Firewall tab and turn it off temporarily.
3. Try visiting the website again.
4. Re-enable firewall: Once done testing, turn the firewall back on.
If disabling the firewall resolves the error, you may need to adjust its settings to allow DNS traffic.
On Windows, you can easily restore the firewall to default settings:
7. Reset Browser to Default Settings
If the ERR_NAME_NOT_RESOLVED error persists, it might be related to your browser’s settings. Updating your browser or resetting it to its default settings can help resolve these issues.
Steps to reset browser settings:
1. In Google Chrome, go to the address chrome://settings/reset and click the Restore settings to their original defaults button > Reset settings
2. In Firefox, go to “about:support” > Refresh Firefox
3. For Microsoft Edge, go to the address edge://settings/reset and click the Restore settings to their default values button.
8. Scan for Malware
Malware can interfere with DNS resolution by altering system settings, blocking certain domains, or redirecting your traffic to malicious servers. This can lead to the ERR_NAME_NOT_RESOLVED error.
Running a malware scan and removing malicious files can help resolve the issue.
8.1. For Windows
Press the Windows + S key combination (or click the Start button) > search for Windows Security > Open it and go to Virus & threat protection > Scan options > select a Quick scan or a Full scan > Scan now
8.2. For macOS
Apple devices have multiple built-in layers of security, but no option to run a manual scan yourself. For that, you need additional third-party tools such as Malwarebytes for Mac.
If malware is found on your device:
- Reset network settings: Malware may have altered your DNS or network configuration. Reset these settings after removing malware.
- Update your system: Install the latest security patches to protect against future infections.
- Change passwords: Update passwords for critical accounts, as they may have been compromised.
Once your system is clean, check if the ERR_NAME_NOT_RESOLVED error persists. If you still see it, move on to the last troubleshooting step.
9. Check Hosts File
The hosts file on your device maps domain names to IP addresses. Misconfigurations or unauthorized changes to this file can cause the ERR_NAME_NOT_RESOLVED error.
Steps to check the hosts file:
9.1. For Windows
1. Open the hosts file:
- Press Windows + S, type Notepad, and right-click to choose Run as administrator.
In Notepad, go to File > Open and navigate to the following path:
C:\Windows\System32\drivers\etc\hosts
- Make sure to set the file type to “All Files” to see the hosts file.
2. Inspect the file for misconfigurations:
The default hosts file usually contains only comments (lines starting with #). Look for any additional entries that block or redirect websites, such as:
12.123.12.12 example.com
If there is such a line, it means the website “example.com” would try to load from the address 12.123.12.12, instead of its corresponding IP address.
3. Remove unnecessary entries:
- Delete any suspicious or incorrect lines that block or redirect legitimate websites.
4. Save the file:
- After making changes, click File > Save and close Notepad.
9.2. For macOS
1. Open the hosts file:
- Open the Terminal (press Command + Space, type Terminal, and press Enter).
Type the following command and press Enter:
sudo nano private/etc/hosts
- Enter your administrator password when prompted.
2. Inspect the file for misconfigurations:
- Check for lines that redirect legitimate websites, similar to the Windows instructions.
3. Edit the file:
- Use the arrow keys to navigate and remove unwanted lines.
- To save changes, press Control + O, then Enter. Exit by pressing Control + X.
After updating the hosts file, restart your browser and check if the error is resolved.
What Causes an ERR_NAME_NOT_RESOLVED Error?
The ERR_NAME_NOT_RESOLVED error occurs due to a breakdown in DNS resolution, often caused by misconfigurations or external interferences.
Knowing these causes not only aids in prevention but can also guide you to the right fix if the error occurs again.
1. DNS and Network Misconfigurations
DNS and network misconfigurations are common culprits behind the ERR_NAME_NOT_RESOLVED error.
These issues occur when your system, router, or ISP fails to correctly handle DNS queries, preventing domain names from resolving to IP addresses.
Below are the key causes and explanations:
1.1. Unresponsive DNS Servers
When the DNS server you’re using is down, slow, or overwhelmed, it cannot process requests to resolve domain names. This often happens when:
- Your ISP’s DNS servers are experiencing outages.
- Heavy traffic causes server delays or timeouts.
- The DNS server is configured incorrectly, pointing to an invalid or outdated address.
Solution:
Switch to a reliable third-party DNS, such as:
- Google Public DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare DNS: 1.1.1.1 and 1.0.0.1
These servers are optimized for uptime, speed, and security, reducing the likelihood of such errors.
1.2. Corrupted DNS Cache
The DNS cache temporarily stores domain name resolutions to speed up browsing. However, if this cache becomes outdated or corrupted, it can lead to DNS resolution errors.
How it happens:
- The IP address of a website changes, but your device still tries to use the old address.
- A corrupted cache contains incorrect or incomplete entries.
Solution:
Flush the DNS cache to refresh it.
2. Browser Cache and Cookies
Browser cache and cookies store temporary data to improve page loading times and maintain session information. While helpful, they can cause issues if:
- Stored DNS-related data is outdated.
Websites you visited previously may have moved to a new server, making cached entries invalid. - Corrupted cookies conflict with the DNS resolution process.
This can happen if a website’s cookies contain outdated or incorrect data.
Solution:
Clear your browser cache and cookies, or reset to default settings to force a fresh DNS query.
3. Malware or DNS hijacking
Malware infections or DNS hijacking can tamper with your DNS settings or redirect your requests to malicious servers. This is often done to intercept your data or display unwanted ads.
Solution:
- Run a full malware scan using trusted software like Malwarebytes or Windows Defender.
- Check your DNS settings for unauthorized changes (e.g., unexpected server addresses).
- Restore your DNS settings to a trusted configuration, such as Google or Cloudflare.
4. Firewall Conflicts
Firewalls play important roles in securing your network, but they can sometimes interfere with DNS resolution.
Overly restrictive settings or misconfigurations may block DNS requests and lead to the ERR_NAME_NOT_RESOLVED error.
How Firewalls Cause Issues
- Strict Rules Block DNS Queries: Some firewalls may block outbound requests to DNS servers, especially if they are not recognized as trusted.
- Application-Specific Restrictions: A firewall may block specific browsers or applications from making DNS queries.
- Misconfigured Settings: Incorrect firewall rules or manual customizations can inadvertently block legitimate traffic.
Solution:
- Temporarily disable your firewall and test whether the error persists.
- If disabling resolves the issue:
- Review and adjust your firewall settings to allow DNS traffic.
- Add your DNS server as a trusted address or whitelist the browser in the firewall settings.
- Reset your firewall to default settings.
Other Potential Causes
We’ve explored issues that users can address locally to fix the ERR_NAME_NOT_RESOLVED error.
Unfortunately, sometimes the underlying cause may be outside of our control.
If you’ve gone through all steps we described above, and are still facing the error, it’s most likely a more complex issue.
This could be a problem with your internet provider, device hardware, or the domain name of the website you are trying to visit.
Final Thoughts on Fixing ERR_NAME_NOT_RESOLVED
The ERR_NAME_NOT_RESOLVED error can be frustrating, but it is usually straightforward to resolve by following systematic troubleshooting steps.
Understanding the common causes – such as DNS misconfigurations, browser cache issues, or interference from firewalls – can help prevent the error from reoccurring.
Keeping software updated, and using trusted DNS servers like Google or Cloudflare can enhance overall browsing stability.
By following this guide, most users should be able to fix the error effectively. If the issue persists after trying these steps, it may indicate deeper problems, such as ISP-related DNS issues, local DNS misconfigurations or hardware malfunctions.
In such cases, we recommend contacting the website hosting provider or an IT support team that can provide additional guidance.
Want to learn more about DNS and network troubleshooting? Download our comprehensive ebook – it is all that you need to solve similar errors with ease!
