Learn how to fix the ERR_NAME_NOT_RESOLVED error. Our CloudFlare Support team is here to answer queries and concerns.
How to Fix the ERR_NAME_NOT_RESOLVED Error
If you encounter the ERR_NAME_NOT_RESOLVED error while browsing, you’ve come to the right place.
This is a common issue, and there are several ways to resolve it.
Today, we will examine the most common causes of the ERR_NAME_NOT_RESOLVED error and how to fix them.
An Overview:
What Is the ERR_NAME_NOT_RESOLVED Error?
The ERR_NAME_NOT_RESOLVED error typically means that the browser couldn’t find the IP address that matches the website’s domain name. In other words, the device failed to resolve the domain name into a usable IP address.
This can be caused by a variety of issues, including DNS problems, cache conflicts, network issues, or misconfigured browser settings. If you’re working with Cloudflare, our guide on Cloudflare geofencing provides helpful context on how location-based rules can impact site accessibility.
How to Fix the ERR_NAME_NOT_RESOLVED Error
1. Test the Internet Connection
Before diving into technical fixes, ensure the internet connection is stable.
Try accessing the same website from another Wi-Fi network or a mobile hotspot. If the site loads, try restarting the router or modem to resolve any temporary network issues.
If you’re managing a website through a content delivery network like Cloudflare, ensure that there are no additional restrictions, such as device or browser filters, that may interfere. Learn more about such configurations in our post on Cloudflare Access Device Posture Check.
2. Clear the DNS Cache
The computer stores DNS information to load websites faster, but this cache can become outdated or corrupted.
- For Windows:
Open the Command Prompt and enter the following command:
ipconfig /flushdns - For macOS:
Open the Terminal and type:
dscacheutil -flushcache - For Linux:
Depending on the distro, use one of the following:
sudo /etc/init.d/nscd restartOr
systemd-resolve –flush-cachesThen confirm with:
systemd-resolve –statistics
After clearing the DNS cache, try reloading the website.
3. Check the Browser Settings
Browsers can store their own DNS information, which might be outdated.
To clear Chrome’s DNS Cache, open Chrome and go to chrome://net-internals/#dns
Then, click Clear host cache.
To disable preload pages, go to Chrome Settings > Privacy and security > Cookies and other site data. Then, toggle off Preload pages for faster browsing and searching.
To clear the Browser cache, go to Settings > Privacy and security > Clear browsing data. Then, set the time range to All time, select all checkboxes, and click Clear data.
If we are using a different browser, clear its cache using the correct method.
Additionally, if you notice unusual behavior in the browser after DNS changes, check for caching issues at the CDN level. We recently explored how misconfigurations can lead to similar browsing problems in our Cloudflare bypass error guide.
4. Reset the Firewall Settings
Security programs and firewalls may mistakenly block legitimate websites.
On Windows:
- Open Settings > Privacy & Security > Windows Security.
- Click Firewall & network protection.
- Select Restore firewalls to default.
This will reset any custom rules that might be interfering with DNS resolution.
5. Change the DNS Server Settings
The DNS server might be unresponsive. Switching to a public DNS, like Google’s, can help.
For Windows:
- Go to Control Panel > Network and Sharing Center > Change adapter settings.
- Right-click the active connection and choose Properties.
- Then, select Internet Protocol Version 4 (TCP/IPv4), then click Properties.
- Choose Use the following DNS server addresses and enter:
Preferred DNS server: 8.8.8.8
Alternate DNS server: 8.8.4.4
For macOS:
- Go to System Preferences > Network > Advanced > DNS.
- Click the `+` icon and add:
8.8.8.8
8.8.4.4
- Click OK, then Apply.
Once updated, retry accessing the website. If you’re using a DNS security layer or firewall service in combination with TLS, check out our breakdown of potential DNS and encryption conflicts in Cloudflare TLS handshake issues.
6. Disable DNSSEC for the Domain
If we are trying to access our own website, and we have recently changed hosting providers, DNSSEC could be causing issues.
- Run a WHOIS search to see if DNSSEC is enabled.
- If it’s marked as “signed”, disable it via the domain registrar or hosting control panel.
If we can’t access the DNS settings, our Experts can help.
[Need assistance with a different issue? Our team is available 24/7.]
Conclusion
The ERR_NAME_NOT_RESOLVED error can be easily fixed with a few quick tweaks.
In brief, our Support Experts demonstrated how to set up a DHCP Server with a GUI on a Raspberry Pi.
0 Comments