DNS troubleshooting
DNS issues stop your site dead. Unlike uptime problems — where the server is at fault — DNS failures mean visitors can't even find your site in the first place. The browser never makes a connection; it just returns "This site can't be reached." DomainDash's DNS checks catch these problems within minutes so you know before visitors tell you.
If you're not sure which DNS issue you have, the domain not resolving page helps you route from the error code or symptom to the right fix.
Resolution failures
Problems where your domain can't be translated into an IP address.
- No A or AAAA records — the domain has no records pointing it to a server. The most common cause of
NXDOMAINerrors. Usually a deleted or missing record in your DNS provider's dashboard. - Nameservers unreachable — the servers responsible for your domain's DNS aren't responding. Could be a DNS provider outage or misconfigured NS records at your registrar.
Propagation and changes
Problems that appear after you've made a DNS change.
- DNS changes not propagating — you've updated DNS but the new records aren't showing everywhere yet. Explains how TTLs and resolver caching affect propagation, and what you can (and can't) do to speed it up.
Not sure where to start?
- Domain not resolving — a routing page from the user-facing symptom ("my domain doesn't work") to the specific DNS issue and how to fix it.
Related
- DNS health — how DomainDash runs DNS checks and what the results mean
- DNS resolution failed — what happens when uptime checks fail because of DNS (a related but distinct error)
- How incidents work — how DomainDash confirms and notifies about DNS failures