What Is ERR_NAME_NOT_RESOLVED Error And How To Fix It

Encountering the ERR_NAME_NOT_RESOLVED error can be frustrating and disruptive, particularly when you’re trying to access an important or urgent website. This error is displayed by browsers such as Chrome, Firefox, and Edge when the Domain Name System (DNS) fails to translate a domain name into its corresponding Internet Protocol (IP) address. DNS is a fundamental service that translates human-friendly website addresses (URLs) into numerical IP addresses that computers understand. When DNS resolution fails, browsers can’t establish a connection, resulting in the ERR_NAME_NOT_RESOLVED error.

What Causes ERR_NAME_NOT_RESOLVED?

The ERR_NAME_NOT_RESOLVED error can occur due to several common reasons, each impacting your browsing experience differently:

1. Incorrect URL: One of the simplest and most frequent causes is an incorrect website URL. This includes typos, misspellings, unnecessary spaces, or accidental additional characters that lead to domain resolution failure.

2. DNS Server Issues: If your DNS server is temporarily down, slow, or experiencing technical issues, it cannot process DNS requests efficiently, resulting in resolution failures and the ERR_NAME_NOT_RESOLVED error.

3. DNS Cache Problems: Your operating system and browser store previously resolved domain names to speed up future access. However, this cache can become outdated or corrupted, causing the DNS to resolve to incorrect IP addresses and leading to errors.

4. Misconfigured Network Settings: Incorrect or outdated DNS server settings on your device can disrupt the proper functioning of DNS queries. If your system attempts to connect to an inactive or misconfigured DNS server, you will encounter resolution problems.

5. Firewall or Antivirus Restrictions: Security software such as firewalls, antivirus, or network security tools can inadvertently block DNS queries. This usually happens when these tools are overly restrictive or misconfigured, mistakenly identifying legitimate DNS requests as harmful activities, thus blocking access to certain websites.

Step-by-Step Solutions to Fix ERR_NAME_NOT_RESOLVED

1. Double Check the URL

Before diving into technical fixes, ensure the website address you’ve typed is correct. A simple typo in the domain name or an extra space can cause the browser to fail in resolving the site. Even an unnoticed mistake like .co instead of .com or a misplaced character can trigger this error.

Solution: Carefully check the URL for any errors or unnecessary spaces. If possible, try accessing the website using a different device to verify that the issue is not due to a typo.

2. Verify DNS Resolution

• Check if DNS resolution is functioning correctly by querying it from the command line:

  Windows (Command Prompt or PowerShell):

  • Using nslookup:

    nslookup example.com
    

  • Using ping (for basic resolution):

    ping example.com
    

  • Using Resolve-DnsName (PowerShell only):

    Resolve-DnsName example.com
    

  Linux/Mac (Terminal):

  • Using dig (most detailed):

    dig example.com
    

  • Using nslookup:

    nslookup example.com
    

  • Using host:

    host example.com
    

  • Using ping (for basic resolution):

    ping example.com
    

These commands help confirm whether DNS resolution is functioning correctly and can identify if the issue lies with DNS settings or connectivity.

If DNS lookup is successful, the output will display the resolved IP address of the domain (e.g., Name: example.com Address: 93.184.216.34).

If DNS lookup fails, the output will indicate an error such as Non-existent domain, NXDOMAIN, or connection timed out; no servers could be reached.

3. Clear DNS Cache

Your computer stores DNS information in a local cache to speed up future visits to websites. However, if this cache becomes outdated or corrupt, it can cause the ERR_NAME_NOT_RESOLVED error. Clearing the DNS cache forces your device to obtain fresh DNS information from your DNS server.

Solution:

• Windows:
  1. Press Windows + R to open the Run dialog.
  2. Type cmd and hit Enter to open Command Prompt.
  3. Type ipconfig /flushdns and press Enter to clear the DNS cache.
• macOS:
  1. Open Terminal (use Spotlight to search for it).
  2. Type sudo dscacheutil -flushcache and press Enter.
  3. You may be asked to enter your administrator password.

After clearing the cache, retry visiting the website.

4. Change DNS Servers

If the default DNS server you are using is slow or unreliable, switching to a different, more reliable DNS provider can help resolve the issue. Google DNS and Cloudflare DNS are popular choices that often provide faster and more reliable service.

Solution:

• Windows:
  1. Go to Control Panel > Network and Internet > Network Connections.
  2. Right-click on your active network connection, then click Properties.
  3. Choose “Internet Protocol Version 4 (TCP/IPv4)” and click Properties.
  4. Select “Use the following DNS server addresses” and enter:
     • Preferred DNS server: 8.8.8.8 (Google DNS)
     • Alternate DNS server: 8.8.4.4 (Google DNS)
• macOS:
  1. Go to System Preferences > Network.
  2. Select your active network connection (Wi-Fi or Ethernet), then click Advanced.
  3. Go to the DNS tab and click the + button to add:
     • 8.8.8.8 (Google DNS)
     • 8.8.4.4 (Google DNS)

This change forces your device to use a new DNS provider for resolving domain names.

5. Clear Browser Cache and Cookies

Your browser’s cache and cookies can sometimes interfere with DNS resolution. Clearing the cache can help resolve any issues caused by outdated or corrupt files.

Solution:

• Open your browser settings, go to Privacy or History settings, and clear browsing data, including cached images, cookies, and other site data.
• Restart your browser and try to visit the website again.

6. Disable Browser Prediction Services

Browsers like Chrome use predictive algorithms to preload pages, which can sometimes interfere with DNS resolution. Disabling these services might resolve the error.

Solution:

1. Open Chrome and go to Settings.
2. Navigate to Privacy and Security.
3. Disable the option “Preload pages for faster browsing and searching.”

Disabling this setting can stop Chrome from attempting to pre-resolve websites that might conflict with DNS settings.

7. Check Your Firewall and Antivirus Settings

In some cases, your firewall or antivirus software might block DNS queries, causing the error. Disabling your firewall or antivirus temporarily can help determine if they are the cause.

Solution:

• Temporarily disable your firewall or antivirus software.
• If the website loads, adjust your firewall or antivirus settings to allow DNS queries, or whitelist the website you’re trying to access.

Make sure to enable your firewall or antivirus again after troubleshooting.

8. Verify Your Hosts File

The hosts file on your computer contains mappings of IP addresses to domain names. If there are incorrect entries in this file, it could block access to certain websites.

Solution:

• Windows:
  1. Open File Explorer and navigate to C:\Windows\System32\drivers\etc\hosts.
  2. Open the file in a text editor (e.g., Notepad).
  3. Remove or correct any incorrect entries.
• macOS:
  1. Open Terminal and type sudo nano /etc/hosts.
  2. Review the file and remove any incorrect mappings.
  3. Save the file and exit (press CTRL + X, then Y to confirm, and Enter).

Once the hosts file is corrected, try reloading the website.

Step 1: Launch Your Foundry VTT Server Locally

To begin, ensure your Foundry VTT instance is running on your local machine. By default, Foundry operates on port 30000.

1. Start the Foundry VTT Application
   Launch the Foundry VTT application as you normally would.

2. Check Local Network Access
   Navigate to Game > Access > Local Network within the Foundry interface. Here, you’ll see the local network address where Foundry is running, such as:

   http://10.123.1.136:30000
   

3. Verify the Server is Running
   Open your web browser and go to:

   http://localhost:30000
   

   If everything is set up correctly, you should see the Foundry VTT login page or welcome screen.

How to Prevent ERR_NAME_NOT_RESOLVED Errors in the Future

Regularly Update Software and Drivers

Keep your browser and network drivers updated to ensure compatibility and stability.

Use Reliable DNS Services

Consider using reputable DNS providers like Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1) for reliable performance and better security.

Periodically Clear DNS Cache

Regularly clearing your DNS cache prevents outdated information from causing connectivity issues.

Maintain Proper Security Settings

Regularly review your firewall and antivirus configurations to prevent accidental blocking of legitimate DNS queries.

Recommended Tools

• Cloudflare DNS (1.1.1.1): A fast, secure, and privacy-focused DNS resolution service.
• Google DNS (8.8.8.8, 8.8.4.4): Widely used and reliable DNS solution.
• DNS Jumper: An easy-to-use tool that helps quickly switch between DNS providers, improving browsing speed and reliability.

By following these comprehensive steps, you’ll effectively resolve and prevent ERR_NAME_NOT_RESOLVED errors, ensuring smooth and uninterrupted internet browsing.

Fixing ERR_NAME_NOT_RESOLVED Errors for Pinggy URLs

Pinggy dynamically assigns DNS records when a tunnel is created. This means that if your browser queries the URL before the tunnel is fully set up, you may encounter the ERR_NAME_NOT_RESOLVED error. However, the Time-To-Live (TTL) for Pinggy’s DNS records is only 10 seconds. As a result, after waiting for around 10 to 15 seconds, refreshing the page should resolve the issue and allow the URL to load successfully.

Conclusion

The ERR_NAME_NOT_RESOLVED error can be caused by a variety of factors, from simple typing mistakes to more complex network or DNS configuration problems. By following the above step-by-step troubleshooting methods, you can resolve most issues and get back to browsing without interruptions.