TL;DR: Quick Fixes for ERR_NAME_NOT_RESOLVED

When you hit This site can't be reached. ERR_NAME_NOT_RESOLVED, it means your computer couldn't translate the website's name (like example.com) into an IP address. This is almost always a DNS issue. Here are the fastest ways I usually try to get things working again:

• Restart your router/modem: Seriously, this fixes a surprising number of network issues. Just unplug it for 30 seconds, then plug it back in.

• Clear your browser's DNS cache:

  Chrome: Go to chrome://net-internals/#dns and click "Clear host cache".

  • Firefox: Restart the browser.

• Flush your operating system's DNS cache:

  Windows: Open Command Prompt as administrator and run ipconfig /flushdns.

  • macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
  • Linux (systemd-resolved): Open Terminal and run sudo resolvectl flush caches or sudo systemctl restart systemd-resolved.

• Change your DNS server: Temporarily switch to a public DNS server like Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1) in your network adapter settings.

• Try another browser or device: If it works elsewhere, the problem is specific to your current browser or machine.

Detailed Root Cause: What's Happening with Name Resolution?

The ERR_NAME_NOT_RESOLVED error pops up when your browser fails to convert a human-readable domain name (e.g., google.com) into a machine-readable IP address (e.g., 172.217.160.142). This conversion process is handled by the Domain Name System (DNS).

Think of DNS as the internet's phone book. When you type a website address, your computer asks a DNS server for the corresponding IP address. If the DNS server can't be reached, or if it doesn't have an entry for that domain, or if your local configuration is messed up, you get this error.

Common reasons for this failure include:

• Local DNS cache corruption: Your computer or browser might have old or bad DNS records cached.
• Incorrect DNS server configuration: Your computer or router might be pointing to a non-existent or unresponsive DNS server.
• Router/modem issues: The device responsible for connecting you to the internet might be glitching.
• Firewall or antivirus interference: Security software can sometimes block DNS queries.
• VPN/Proxy issues: If you're using one, it might be misconfigured or having issues.
• hosts file entries: Incorrect entries in your local hosts file can override DNS lookups.
• ISP (Internet Service Provider) problems: Your ISP's DNS servers might be down or experiencing issues.
• Website-specific DNS issues: Less common for popular sites, but the website's own DNS records might be misconfigured or propagating slowly.

Fix Approaches

Let's go through the troubleshooting steps in more detail.

1. Browser-Specific Troubleshooting

Sometimes the issue is confined to your browser.

• Clear Browser DNS Cache

  Browsers often maintain their own DNS cache.

  Chrome: Type chrome://net-internals/#dns into the address bar and click "Clear host cache".

  • Firefox: Simply restarting Firefox usually clears its internal cache.

• Disable DNS Prefetching / QUIC Protocol

  These features can sometimes cause issues. Try disabling them temporarily.

  Chrome: Go to chrome://settings/security and toggle off "Preload pages for faster browsing and searching" or "Use secure DNS" temporarily. For QUIC, go to chrome://flags/#enable-quic and set it to "Disabled".

  • Firefox: Type about:config, search for network.dns.disablePrefetch and set it to true. Also check network.http.speculative-parallel-limit and set it to 0.

• Test in Incognito/Private Mode

  This bypasses extensions and cached data, which can help isolate the problem.

2. Local Machine DNS Cache

Your operating system also caches DNS records. Flushing it can resolve stale entries.

• Windows

ipconfig /flushdns

  
  - 
    #### macOS
    ```bash
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

• Linux

  Depending on your distribution and DNS resolver:

  systemd-resolved (common in Ubuntu, Fedora): ```bash sudo resolvectl flush caches

Or restart the service

sudo systemctl restart systemd-resolved

      
      - **nscd (older systems):**
        ```bash
sudo /etc/init.d/nscd restart

  - **dnsmasq:**
    ```bash

sudo /etc/init.d/dnsmasq restart

      
    
  

### 3. Network Configuration: DNS Servers
This is where you tell your computer which DNS servers to use.

  - 
    #### Check Current DNS Settings
    
      **Windows:** Open Command Prompt and run `ipconfig /all`. Look for "DNS Servers" under your active network adapter.
      - **macOS:** Open Terminal and run `scutil --dns`.
      - **Linux:** Check `/etc/resolv.conf` or use `resolvectl status` (if using systemd-resolved).
    
  
  - 
    #### Change DNS Servers
    Temporarily switch to reliable public DNS servers like Google (`8.8.8.8`, `8.8.4.4`) or Cloudflare (`1.1.1.1`, `1.0.0.1`).

    
      **Windows:** Go to "Network and Internet Settings" > "Change adapter options". Right-click your active adapter (Ethernet or Wi-Fi), select "Properties", then "Internet Protocol Version 4 (TCP/IPv4)", "Properties". Select "Use the following DNS server addresses" and enter them.
      - **macOS:** Go to "System Settings" > "Network". Select your active connection, click "Details", then "DNS". Add the new DNS servers.
      - **Linux:** This depends on your network manager. For NetworkManager, you can often do it via GUI. Command line options involve editing `/etc/resolv.conf` (though changes might be overwritten) or configuring NetworkManager directly. Example for NetworkManager with nmcli:
        ```bash
nmcli con show # Find your connection name, e.g., "Wired connection 1"
nmcli con mod "Wired connection 1" ipv4.dns "8.8.8.8 8.8.4.4"
nmcli con mod "Wired connection 1" ipv4.dns-search ""
nmcli con up "Wired connection 1"

4. Router/Modem Issues

Your router acts as a local DNS forwarder or points to your ISP's DNS servers.

• Restart Router

  A simple reboot can clear up many intermittent network problems, including DNS resolution issues.

• Check Router's DNS Settings

  Log into your router's admin panel (usually via 192.168.1.1 or 192.168.0.1) and verify its DNS configuration. Ensure it's not pointing to invalid servers.

5. Firewall or Antivirus Interference

Sometimes security software can be overzealous.

• Temporarily Disable

  As a test, temporarily disable your firewall or antivirus. If the site loads, you've found your culprit. Remember to re-enable it and then investigate specific rules.

6. Proxy Settings

If you're using a proxy, it might be misconfigured or down.

• Check System/Browser Proxy Settings

  Ensure no incorrect proxy settings are enabled. In Windows, go to "Internet Options" > "Connections" > "LAN settings". On macOS, "System Settings" > "Network" > "Details" > "Proxies".

7. Hosts File

Your local hosts file can override DNS and point a domain to a specific IP.

• Check for Incorrect Entries

  Ensure there are no erroneous entries for the domain you're trying to reach.

  Windows: C:\Windows\System32\drivers\etc\hosts

  • macOS/Linux: /etc/hosts

  Open with a text editor (as administrator on Windows, with sudo on macOS/Linux).

8. ISP Issues or Website-Specific Problems

If all local troubleshooting fails, the problem might be outside your control.

• Test with Mobile Hotspot

  Connect your computer to your phone's mobile hotspot. If the site works, the issue is with your home network or ISP.

• Use Online Tools

  Check if the website is down for everyone or just you using sites like downforeveryoneorjustme.com.

• Contact Your ISP

  If the issue persists and seems to be network-wide, your ISP might be experiencing DNS server problems.

Verification Steps

After trying a fix, confirm it worked:

• Ping the domain:

ping example.com

If it returns an IP address and successful replies, DNS resolution is working.

  
  - **Use `nslookup` or `dig`:**
    ```bash
nslookup example.com
# Or for more detail
dig example.com

These tools will show you which DNS server resolved the name and the IP address it returned.

• Try the browser again: Open a new browser window or tab and try to access the website.

Prevention & Tips

• Use reliable DNS servers: Sticking with well-known public DNS providers (Google, Cloudflare, OpenDNS) can offer better reliability and sometimes speed compared to default ISP servers.
• Keep OS and browser updated: Updates often include network stack improvements and bug fixes.
• Regular router reboots: A quick reboot every few weeks can help keep your network gear fresh.
• Network configuration review: Periodically check your network adapter settings and router configuration, especially after system updates or network changes. For quick checks of your local network setup, like ensuring your IP address, gateway, and DNS server are all on the expected subnet, I sometimes use tools like the Subnet Calculator on ToolCraft. It's handy for confirming your basic network configuration is sound, which can indirectly impact DNS resolution if your machine can't even reach its configured DNS server.

Further Reading

• Cloudflare: What is DNS?
• How-To Geek: The Ultimate Guide to Changing Your DNS Servers