Skip to main content

ERR_NAME_NOT_RESOLVED: fix the DNS error in Chrome and Edge (Windows 11 and 10)

ERR_NAME_NOT_RESOLVED means the site's name was not translated into an IP address. Test DNS, clear the caches, check the hosts file and internal DNS.

Published 14 November 2026 · 5 min read

ERR_NAME_NOT_RESOLVED is misleading: Wi-Fi is connected, email sometimes still works, yet one site refuses to open. The network is fine, it is the directory that does not answer. DNS, which translates a name such as www.example.com into an IP address, has failed, and the browser does not know where to go.

The short answer

ERR_NAME_NOT_RESOLVED (or net::ERR_NAME_NOT_RESOLVED) means Chrome or Edge could not translate the site's name into an IP address. Check the spelling of the address, test the name with nslookup or Resolve-DnsName, look at the device's DNS servers with ipconfig /all, clear the Windows and browser DNS caches, then check the hosts file. In a company, the culprit is often the internal DNS or the VPN. With a tool like LongLife, the network quality of every device is tracked continuously and included in the DEX score, which shows whether the problem affects one device or a whole site.

What the code means

In Chromium's official list of network errors (Chromium is the engine behind Chrome and Edge), NAME_NOT_RESOLVED has the number -105: the host name could not be resolved. If the device has no network at all, the browser shows ERR_INTERNET_DISCONNECTED instead, covered in our ERR_INTERNET_DISCONNECTED guide. If the connection changes while the page loads, it is ERR_NETWORK_CHANGED; a browser cache error gives ERR_CACHE_MISS.

Start with the obvious: a typo in the address, or a site whose domain name has expired, produce exactly the same error. Try another well-known site: if that one works, the problem may be on the side of the site you want.

Step 1: test name resolution

In PowerShell, query DNS the way Windows does:

PowerShell
Resolve-DnsName -Name www.example.com
Resolve-DnsName -Name www.example.com -Server 1.1.1.1

The first command uses the device's DNS servers, the second a public server. If only the first fails, the device's DNS server is at fault. If both fail with "DNS name does not exist", the domain does not exist or no longer exists.

nslookup runs the same test from Command Prompt:

Command Prompt
nslookup www.example.com
nslookup www.example.com 1.1.1.1

A useful difference: nslookup queries the DNS server directly and ignores the hosts file and the Windows cache, whereas Resolve-DnsName follows the normal Windows path. If nslookup answers but the browser does not, look at the hosts file and the caches (steps 3 and 4).

Step 2: see which DNS servers the device uses

Command Prompt
ipconfig /all

Find the DNS Servers line for the active adapter. In PowerShell, the list is easier to read:

PowerShell
Get-DnsClientServerAddress -AddressFamily IPv4

An unexpected address (an old server, a DNS left behind by an uninstalled VPN or by unwanted software) often explains everything.

Step 3: clear the DNS caches

Windows keeps DNS answers in memory, failures included. Clear that cache in Command Prompt run as administrator:

Command Prompt
ipconfig /flushdns

or in PowerShell run as administrator:

PowerShell
Clear-DnsClientCache

Chrome and Edge have their own cache: open chrome://net-internals/#dns (or edge://net-internals/#dns) and click Clear host cache. Then close and reopen the browser.

Step 4: check the hosts file

The file C:\Windows\System32\drivers\etc\hosts takes precedence over DNS. A forgotten line can redirect a site to a dead address. Display the active lines:

PowerShell
Get-Content C:\Windows\System32\drivers\etc\hosts | Where-Object { $_ -notmatch '^\s*#' -and $_.Trim() }

If nothing is displayed, the file is neutral. Otherwise, open it in Notepad run as administrator and remove the line for the site.

Step 5: change DNS server, with care

On a personal or standalone device, switching temporarily to a public DNS confirms the diagnosis. In PowerShell run as administrator, using the adapter name shown by Get-NetAdapter:

PowerShell
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ServerAddresses ("1.1.1.1","8.8.8.8")

To go back to the servers provided automatically (DHCP):

PowerShell
Set-DnsClientServerAddress -InterfaceAlias "Wi-Fi" -ResetServerAddresses

In a company, do not do this on a domain-joined device: it must use the internal DNS servers, otherwise sign-in, Group Policy and internal applications stop working.

One last setting in the browser: Chrome's secure DNS (Settings > Privacy and security > Security > Use secure DNS). An unreachable custom provider causes errors; try turning it off. According to Google, this option is not available on a managed device.

In a company: internal DNS and VPN

  • Internal names: an intranet or an application ending in .local or .lan only resolves through the company's DNS servers. Away from the office and without the VPN, the error is expected.
  • VPN and split DNS: many VPNs send only company names to the internal DNS and leave everything else to the local DNS. If the tunnel drops or the rules are pushed incorrectly, those names no longer resolve. The per-domain resolution rules can be read with:
PowerShell
Get-DnsClientNrptPolicy
  • Internal DNS server down: if every device on a site shows the error for the same names, the problem is on the server side, not the device.

Symptoms, causes and fixes

What you seeLikely causeWhat to do
A single site fails, everywhereTypo, expired domainCheck the address, wait for the site
Resolve-DnsName fails, works with -Server 1.1.1.1Device's DNS server downCheck ipconfig /all, DHCP or internal DNS
nslookup answers, the browser does notHosts file, cacheipconfig /flushdns, browser cache, hosts file
Internal names fail away from the officeVPN down, split DNSReconnect the VPN, check the NRPT rules
All devices on a site affectedInternal DNS or routerCheck the site's DNS server

For other frequent issues at the office, see our overview of common IT problems.

LongLife: know whether it is one device or the whole site

This guide fixes one device. LongLife gives you the view across your whole fleet:

  • measure: LongLife tracks the network quality of every device and includes it in the DEX score (startup, network, stability, satisfaction);
  • detect: detectors analyse your fleet continuously and suggest the recommended action, with its priority and the cost of doing nothing;
  • locate: devices grouped by site and department show whether the issue affects one device, one floor or a whole branch;
  • act remotely: a catalogue of signed scripts, written and tested by OPP! and expanded with every update, runs on the devices you choose, with a report for each device.

The free plan covers up to 15 devices. Estimate what you would gain with the simulator, or book a meeting to see your own devices in LongLife.

Sources

Frequently asked questions

What does ERR_NAME_NOT_RESOLVED mean?

The browser could not translate the site's name (for example www.example.com) into an IP address. The network connection may work perfectly: it is DNS resolution that fails, because of a typo, a stale cache, an unreachable DNS server, the hosts file, or a site whose domain no longer exists.

How do I clear the DNS cache in Windows?

In Command Prompt run as administrator, run ipconfig /flushdns, or in PowerShell run as administrator, Clear-DnsClientCache. Chrome and Edge also have their own cache, which you clear from the chrome://net-internals/#dns page (edge://net-internals/#dns for Edge) with the Clear host cache button.

Should I switch to a public DNS such as 1.1.1.1 or 8.8.8.8?

On a personal device, it is a useful test and often a fix. On a company device joined to Active Directory, no: the device must use the internal DNS servers to find the domain, servers and internal applications. A public DNS then breaks sign-in, Group Policy and the intranet.

Why does the site work on my phone but not on my PC?

The two devices do not necessarily use the same DNS server or the same cache. On the PC, check in this order the hosts file, the Windows and browser DNS caches, the VPN and Chrome's secure DNS. Compare with Resolve-DnsName to see what the PC actually gets.

How much longer can your fleet last?

The simulator estimates in one minute the budget and CO₂ saved by extending your renewal cycle.

Read next