What does the error really mean?
Before connecting, the browser uses DNS to find the IP address associated with a domain. With ERR_NAME_NOT_RESOLVED, this step did not produce a usable result. This differs from ERR_CONNECTION_REFUSED, where the address is known but the connection is refused.
The fastest diagnostic steps
- Verify the exact spelling of the domain and subdomain.
- Open DNS lookup and inspect A, AAAA or CNAME records.
- If a public record exists, compare a different device or mobile data.
- If the domain fails everywhere, check its domain registration and nameservers.
ERR_NAME_NOT_RESOLVED versus DNS_PROBE_FINISHED_NXDOMAIN
DNS_PROBE_FINISHED_NXDOMAIN is a more specific signal that the requested DNS name does not exist. ERR_NAME_NOT_RESOLVED is a broader browser result and may also arise from a resolver timeout or a local DNS issue.
What can a visitor do?
If other sites work, investigate this domain first. If multiple domains fail, reconnect your network, compare without VPN or private DNS, and clear the local DNS cache if necessary. On Windows, a common diagnostic command is ipconfig /flushdns.
If you own the domain
Check nameserver delegation, the existence of the DNS zone and the exact record for the hostname. For migrations also verify DNSSEC: an old DS delegation with new keys can make validating resolvers reject records that otherwise exist. Account for TTL values and resolver caches.
Frequently asked questions
Does ERR_NAME_NOT_RESOLVED mean the server is down?
Not necessarily. The browser may not even have reached the server because it could not obtain a usable DNS address.
Can changing DNS servers help?
It can if the resolver or its cache is at fault. It cannot help when the public DNS record is missing.
Why does the domain work on my phone but not my computer?
Common causes include local DNS caching, VPN, private DNS, a hosts-file entry or a network setting.