Server DNS address could not be found: Chrome's plain-English DNS failure message

The human-readable wrapper Chrome shows around a DNS failure. The technical code underneath — usually DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED — is the one that tells you which fix applies.

Short answer

The human-readable wrapper Chrome shows around a DNS failure. The technical code underneath — usually DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED — is the one that tells you which fix applies.

What Server DNS address could not be found means

Chrome shows this heading whenever name resolution fails for any reason. It is worth reading the smaller code beneath it: a definitive NXDOMAIN and a resolver timeout need completely different fixes.

Causes and fixes, most likely first

1. The hostname has no DNS record. Add the A or CNAME record at the DNS provider and wait out the TTL.
2. The resolver in use is failing or slow. Switch to a public resolver and retry to confirm.
3. The domain registration lapsed. Check the registration status at the registrar. An expired domain removes the zone entirely.

How to stop it happening again

• Monitor domain expiry — a lapsed registration is the one DNS failure no amount of server monitoring will catch.
• Alert on record changes so a bad zone edit is caught in minutes.

Check your own domain

Looking the domain up from outside identifies immediately whether records exist, which is the fork in the road for every fix below.

Frequently asked questions

Is this the same as NXDOMAIN?

Usually, yes — it is the message Chrome shows above the NXDOMAIN code. But it also appears for resolver timeouts, which need a different fix.