Troubleshooting "ERR_NAME_NOT_RESOLVED"

The ERR_NAME_NOT_RESOLVED error (often appearing as "This webpage is not available" or "This site can’t be reached") signals that your browser was unable to find the IP address corresponding to the domain name you entered. It's fundamentally a Domain Name System (DNS) lookup failure.

Verify DNS Records Instantly

Need to see if a domain actually exists or has valid A records? Use our Free Domain & IP Lookup Tool to check the current DNS configuration.

What It Means: DNS Failure

Think of DNS as the internet's phonebook. When you type google.com, your browser asks a DNS server for the numerical IP address of Google's server. If the DNS server can't find or provide that IP address, your browser doesn't know where to send the request, resulting in this error.

Troubleshooting Steps (For Visitors)

Check for Typos: Double-check the spelling of the domain name in the address bar.
Flush Local DNS Cache: Force your OS to clear its stored DNS records. On Windows, open Command Prompt and type ipconfig /flushdns. On macOS, use sudo dscacheutil -flushcache in Terminal.
Change DNS Servers: Configure your device or router to use public DNS servers like Google (8.8.8.8) or Cloudflare (1.1.1.1) instead of your ISP's default servers.

Note for Website Owners

If multiple users report ERR_NAME_NOT_RESOLVED for your site, the problem likely lies with your domain's DNS configuration:

Check Nameserver Settings: Ensure your domain registrar settings point to the correct nameservers provided by your DNS host.
Verify DNS Records: Confirm that the necessary 'A' records pointing to your server's IP address exist and are correct at your DNS host.
Wait for DNS Propagation: If you recently changed nameservers, it can take up to 24-48 hours for the changes to propagate globally.