How to Fix "ERR_NAME_NOT_RESOLVED" Error

#webdev #networking #tutorial #dns

You open your browser, type a web address, hit Enter, and instead of the website you wanted, you’re staring at a cold error message: ERR_NAME_NOT_RESOLVED. Your first instinct might be to panic, refresh, or blame your internet connection. The truth is, this error is one of the most common issues on the web, and in most cases, it’s solvable in under ten minutes once you know what you’re dealing with.

The tricky part? The error message tells you what went wrong but not why or how to fix it. That’s exactly what this guide is for.

I will walk you through what triggers the error, how to isolate the cause, and precisely how to resolve it depending on where the problem lives; your browser, your machine, your network, or the website itself. Let’s dig in.

TL;DR

Quick Troubleshooting Checklist

Before diving into the detailed fixes below, use this quick reference table to identify the most likely cause of the ERR_NAME_NOT_RESOLVED error and the recommended solution.

Now that you have an overview of the possible fixes, let’s understand what this error actually means and why it happens.

What Does ERR_NAME_NOT_RESOLVED Actually Mean?

When you visit a website, your browser doesn’t store the IP addresses of every site on the internet. Instead, it asks a DNS resolver, essentially the internet’s phonebook, to translate a human-readable domain like example.com into a numeric IP address like 192.0.2.1. That process is called a DNS lookup.

ERR_NAME_NOT_RESOLVED is what your browser displays when that lookup failed. The resolver was asked for an address it couldn’t find, couldn’t reach, or didn’t have in its records.

It’s worth noting this is different from DNS_PROBE_FINISHED_NXDOMAIN. The latter specifically means the DNS server was reached and definitively said “this domain doesn’t exist.” ERR_NAME_NOT_RESOLVED is broader, it covers lookup failures for any reason, including network connectivity issues, timeouts, or misconfigured settings on your side.

ERR_NAME_NOT_RESOLVED vs Other Common Browser Errors

Many browser errors look similar but point to different underlying issues. Understanding the difference can help you choose the correct troubleshooting steps more quickly.