---
title: "ERR_NAME_NOT_RESOLVED: What It Means and How to Fix It"
description: "ERR_NAME_NOT_RESOLVED means the browser could not turn a host name into an IP address. Causes and fixes for visitors, developers and site owners."
url: https://uptrack.app/errors/err-name-not-resolved
---

ERR\_NAME\_NOT\_RESOLVED

# ERR\_NAME\_NOT\_RESOLVED: what it means and how to fix it

ERR\_NAME\_NOT\_RESOLVED is the error code Chrome gives when it cannot turn a host name into an IP address. It can appear for the page itself, or in the developer console for an image, a script or an API call on another host.

You may also see

- DNS\_PROBE\_FINISHED\_NXDOMAIN (Chrome, after its DNS probe)
- DNS\_PROBE\_FINISHED\_NO\_INTERNET (Chrome, when there is no connection)
- net::ERR\_NAME\_NOT\_RESOLVED (developer console)

## Common causes

1. 1  
The host name is wrong: a typo in the address, or a wrong API host in an environment variable or a config file.
2. 2  
The name has no DNS record, or the domain has expired.
3. 3  
The device has no working internet connection, or its DNS server does not answer.
4. 4  
A custom name for local development is missing from the hosts file, or a container cannot reach the DNS server of the host.
5. 5  
A blocker, VPN or security program stops the lookup.

## If you are visiting the site: how to fix it

1. 1  
Check that you are online, and that other sites load.
2. 2  
Check the address for a typo, then try it on another network.
3. 3  
Clear the DNS cache of the system and of Chrome (chrome://net-internals/#dns), then reload.
4. 4  
Switch to a public DNS server such as 1.1.1.1 or 8.8.8.8, and turn off a VPN to test.

## If you run the site: what to check

1. 1  
Open the developer console. The failing request shows the exact host name that did not resolve. Compare it with the one you expect.
2. 2  
For a site you run, look up the name and check that it has a record and that the domain is not expired.
3. 3  
For local development, add the name to the hosts file, or use a local DNS tool. In a container, check the DNS server the container uses.
4. 4  
If the name is right and it still fails only for some users, compare the answers of several resolvers.

## Check it with free tools

- [DNS lookupCheck that the host name has a record.](https://uptrack.app/tools/dns-lookup)
- [Domain expiry checkerCheck that the domain is still registered.](https://uptrack.app/tools/domain-expiry-checker)
- [DNS propagation checkerCompare the answers of three resolvers.](https://uptrack.app/tools/dns-propagation-checker)

## Frequently asked questions

What does ERR\_NAME\_NOT\_RESOLVED mean?

Chrome asked for the IP address of a host name and did not get one. It is the general error for a name that cannot be resolved. Chrome often runs a DNS probe next and shows a more exact code such as DNS\_PROBE\_FINISHED\_NXDOMAIN.

What is the difference between ERR\_NAME\_NOT\_RESOLVED and DNS\_PROBE\_FINISHED\_NXDOMAIN?

They are two views of the same kind of failure. ERR\_NAME\_NOT\_RESOLVED is the network error. DNS\_PROBE\_FINISHED\_NXDOMAIN is the result of Chrome’s follow-up DNS probe, which found that the name does not exist.

Why does ERR\_NAME\_NOT\_RESOLVED appear in the console but the page loads?

A resource on the page, such as an image, a script or an API call, points to a host name that does not resolve. The main page loads, but that one request fails. Fix the host name in the code or the configuration.

Can a VPN cause ERR\_NAME\_NOT\_RESOLVED?

Yes. A VPN often sends your DNS questions to its own server. If that server is slow, blocks the name or has a broken setting, the lookup fails. Turn the VPN off to test.

## Know about it before your visitors do

Uptrack checks a DNS record on a schedule and alerts you when it changes or stops resolving, so you learn about a broken record before your visitors report it.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other browser and DNS errors

- [DNS\_PROBE\_FINISHED\_NXDOMAIN](https://uptrack.app/errors/dns-probe-finished-nxdomain)
- [DNS server not responding](https://uptrack.app/errors/dns-server-not-responding)
- [ERR\_CONNECTION\_REFUSED](https://uptrack.app/errors/err-connection-refused)
- [ERR\_CONNECTION\_RESET](https://uptrack.app/errors/err-connection-reset)
- [ERR\_CONNECTION\_CLOSED](https://uptrack.app/errors/err-connection-closed)
- [ERR\_SSL\_PROTOCOL\_ERROR](https://uptrack.app/errors/err-ssl-protocol-error)
- [NET::ERR\_CERT\_AUTHORITY\_INVALID](https://uptrack.app/errors/your-connection-is-not-private)