Fix ERR_NAME_NOT_RESOLVED: Internet Connection Error: ERR_NAME_NOT_RESOLVED (Internet)
The “ERR_NAME_NOT_RESOLVED” error indicates that your browser cannot find the IP address associated with a website’s domain name. This typically means there’s an issue with your Domain Name System (DNS) resolution, which is like the internet’s phonebook. When you type in a website address (e.g., google.com), your computer asks a DNS server to translate that name into an IP address (e.g., 172.217.160.142) so it can connect to the correct server.
🧐 Causes
This error can stem from several common issues:
- Incorrect DNS Server Settings: Your computer might be configured to use a DNS server that is down, overloaded, or incorrectly set up.
- Local DNS Cache Corruption: Your computer stores a local cache of DNS entries to speed up browsing. If this cache becomes outdated or corrupted, it can lead to resolution failures.
- Router Issues: Your router, which often acts as a DNS forwarder for your network, might be experiencing temporary glitches or misconfigurations.
- Firewall or Antivirus Interference: Sometimes, security software can mistakenly block DNS requests.
- Network Connectivity Problems: While the error specifically points to name resolution, underlying network issues can sometimes manifest this way.
- Website Server Issues: In rare cases, the problem might be with the website’s DNS records themselves, though this is less common.

🔧 Fixes
Here are several steps you can take to resolve the “ERR_NAME_NOT_RESOLVED” error:
1. Restart Your Router and Modem
This is often the simplest and most effective fix for temporary network glitches. Unplug both your modem and router from power, wait for about 30-60 seconds, and then plug them back in, starting with the modem first. Wait for all lights to stabilize before testing your connection.
2. Clear Your Browser’s DNS Cache
Your browser stores DNS information. Clearing this cache can force it to fetch fresh DNS data.
- For Chrome: Type
chrome://net-internals/#dnsinto the address bar and click “Clear host cache”. - For Firefox: Type
about:networking#dnsinto the address bar and click “Clear DNS Cache”. - For Edge: Type
edge://net-internals/#dnsinto the address bar and click “Clear host cache”.
3. Flush Your Operating System’s DNS Cache
Similar to the browser cache, your operating system also maintains a DNS cache.
- On Windows: Open Command Prompt as an administrator and type
ipconfig /flushdns, then press Enter. - On macOS: Open Terminal and type
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then press Enter. You will be prompted for your password. - On Linux: The command can vary depending on your distribution, but common commands include
sudo systemd-resolve --flush-cachesorsudo /etc/init.d/nscd restart.
4. Change Your DNS Servers
You can try switching to a public DNS server, such as Google DNS or Cloudflare DNS, which are often faster and more reliable.
- Google DNS: Preferred:
8.8.8.8, Alternate:8.8.4.4 - Cloudflare DNS: Preferred:
1.1.1.1, Alternate:1.0.0.1
You can change these settings in your network adapter properties (Windows) or Network Preferences (macOS/Linux). Consult your operating system’s documentation for specific instructions.
5. Temporarily Disable Firewall/Antivirus
As a diagnostic step, temporarily disable your firewall or antivirus software to see if it’s interfering with DNS resolution. Remember to re-enable it immediately after testing.
6. Check Your Network Adapter Settings
Ensure your network adapter is obtaining an IP address and DNS server address automatically (DHCP) unless you have a specific reason to use static settings.
7. Test with a Different Device or Browser
If the problem persists, try accessing the website from another device on the same network or using a different web browser. This helps determine if the issue is specific to your computer or browser.
🚀 Summary
The “ERR_NAME_NOT_RESOLVED” error means your device can’t translate a website’s name into an IP address, usually due to DNS issues. Common fixes include restarting your router and modem, clearing browser and OS DNS caches, changing DNS servers to public ones like Google or Cloudflare, and ensuring your network settings are correct. In rare cases, temporarily disabling security software or testing on another device can help pinpoint the problem.