Common DNS Errors and How to Read Them
When something goes wrong with a domain, the error messages can look cryptic, but most point to a small set of familiar problems. Learning to read them turns a moment of panic into a quick diagnosis, and helps you give us useful information when you report an issue.
This guide translates the most common DNS errors into plain English and explains what usually causes each one.
Errors You May See
A handful of messages account for the vast majority of DNS problems.
- NXDOMAIN: the name does not exist — often a typo or a missing record.
- SERVFAIL: the name server failed to answer, sometimes a misconfiguration.
- This site can't be reached: DNS resolved but the server did not respond.
- DNS_PROBE_FINISHED_NXDOMAIN: the browser's version of NXDOMAIN.
A Simple Diagnostic Order
Working through a few checks in order usually pinpoints the cause.
- Confirm the domain has not expired.
- Check the relevant DNS record exists and is correct.
- Verify the name servers are set as expected.
- Test from another network to rule out local caching.
Frequently Asked Questions
I see the error but the site works for others — why?
This usually points to local caching or a network issue on your side. Clearing your cache or testing on another connection often confirms it.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.