---
title: "ERR_NAME_NOT_RESOLVED on Chrome: cause and fix"
description: "Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome."
canonical: "https://lemwatch.com/errors/err-name-not-resolved/on-chrome"
source: "https://lemwatch.com"
---

# ERR_NAME_NOT_RESOLVED on Chrome

> Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome.

## Why it happens on Chrome

 Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome.

## The fix on Chrome

 Open chrome://net-internals/#dns → Clear host cache, then chrome://net-internals/#sockets → Flush socket pools. If Secure DNS is on under Settings → Privacy → Security, switch it to 'With your current service provider' to test.

## If that didn't fix it

 Chrome has its own failure mode, but ERR_NAME_NOT_RESOLVED has a wider set of causes. The most common one overall is: No DNS record exists for the hostname.

 Add the A or CNAME record. Check apex and www separately.

## Check your own domain

 Resolving the name from outside your machine proves in one step whether the record exists at all or whether only your resolver is failing.

## Frequently asked questions

### Why does ERR_NAME_NOT_RESOLVED happen on Chrome?

 Chrome keeps its own DNS cache separate from the operating system, so the site resolves in every other app and fails only in Chrome.

### How do I fix ERR_NAME_NOT_RESOLVED on Chrome?

 Open chrome://net-internals/#dns → Clear host cache, then chrome://net-internals/#sockets → Flush socket pools. If Secure DNS is on under Settings → Privacy → Security, switch it to 'With your current service provider' to test.

### What does ERR_NAME_NOT_RESOLVED mean?

 Chrome could not turn the hostname into an IP address. Closely related to NXDOMAIN but broader: it also covers resolver failures and timeouts, not just definitive 'does not exist' answers.


## Related

- [All causes of ERR_NAME_NOT_RESOLVED](https://lemwatch.com/errors/err-name-not-resolved)
- [All website error codes](https://lemwatch.com/errors)
- [ERR_NAME_NOT_RESOLVED on Windows](https://lemwatch.com/errors/err-name-not-resolved/on-windows)
- [ERR_NAME_NOT_RESOLVED on Cloudflare](https://lemwatch.com/errors/err-name-not-resolved/in-cloudflare)
- [ERR_NAME_NOT_RESOLVED on Android](https://lemwatch.com/errors/err-name-not-resolved/on-android)
- [Free DNS lookup](https://lemwatch.com/tools/dns-lookup)
- [Website monitoring overview](https://lemwatch.com/website-monitoring)