🧭
Domains

DNS errors explained: what SERVFAIL, NXDOMAIN and REFUSED mean

16.11.2026
← All articles

When a website will not load, the browser usually shows a short message such as "This site can't be reached" or "DNS_PROBE_FINISHED_NXDOMAIN" and explains almost nothing. In reality every DNS query gets a response code, and that code points straight at the problem. The three most common error codes, SERVFAIL, NXDOMAIN and REFUSED, mean very different things: one says the name does not exist, another says the DNS chain broke somewhere, and the third says a server declined to answer.

Where to see the DNS response code

Browsers hide the code, so you need the command line. Linux and macOS ship dig; on Windows use nslookup or Resolve-DnsName in PowerShell. The header of dig output contains a status: field showing NOERROR, NXDOMAIN, SERVFAIL or REFUSED.

dig misol-klinika.uz A

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41872
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

Note that NOERROR does not always mean a record exists. NOERROR with an empty ANSWER section means the domain exists but has no record of the requested type, for example no AAAA or MX. This is often called NODATA and simply means the record was never added.

NXDOMAIN: the name does not exist

NXDOMAIN is an authoritative statement that the name is not there. The simplest cause is a typo. The next most common is a missing subdomain record: the main domain works, but shop.misol-klinika.uz has no A or CNAME record, so only that name fails. The most serious cause is the domain itself disappearing from the zone, which happens when registration expires and delegation is suspended, or when registration was never completed. Then mail breaks too, because MX records cannot be found either.

whois misol-klinika.uz
dig +trace misol-klinika.uz

dig +trace walks the query down from the root servers. If the .uz servers know nothing about the domain, the issue is registration or delegation. If delegation exists but your name server answers NXDOMAIN, the record is missing from your zone.

SERVFAIL: no answer could be obtained

SERVFAIL usually comes from the recursive resolver your computer uses, such as your ISP's or 8.8.8.8, and means it could not get an answer. Typical causes are all listed name servers being down or unreachable, a lame delegation where the servers set at the registrar do not actually host the zone, and DNSSEC failures. The last one is very common: a DS record remains in the parent zone after a name server change, and the new servers do not sign the zone or sign it with a different key, so validating resolvers reject the answer.

The +cd (checking disabled) flag tells the resolver to skip signature validation. If a normal query returns SERVFAIL and the same query with +cd returns NOERROR, DNSSEC is almost certainly the culprit.

dig @8.8.8.8 misol-klinika.uz A
dig @8.8.8.8 misol-klinika.uz A +cd
dig misol-klinika.uz DS

REFUSED: the server declined

REFUSED means the server received the query but its policy prevents it from answering. Most often you asked an authoritative server about a zone it does not host, for instance after switching name servers before the zone was created on the new server. It also happens when you send a recursive query to a server that only resolves names for its own clients, which is a correct security setting. If a domain's own NS server answers REFUSED, the zone has not been added there.

dig misol-klinika.uz NS +short
dig @ns1.misol-hosting.uz misol-klinika.uz SOA

A real case: a clinic site after moving hosting

A private dental clinic in Tashkent moved its site and changed name servers at the registrar. The next day some patients could not open the site while others could. Through one operator's resolver it returned SERVFAIL, through another it worked, and the query with +cd succeeded. The old provider had DNSSEC enabled, the DS record was still in the parent zone, and the new servers did not sign the zone. Removing the old DS record fixed it once caches expired. The lesson is simple: check DNSSEC before changing name servers.

Quick reference table

CodeMeaningCheck first
NXDOMAINName does not existTypo, subdomain record, expiry and delegation
SERVFAILResolver got no answerNS servers, DNSSEC with +cd, lame delegation
REFUSEDServer declinedIs the zone on that server, are you asking the right one
NOERROR, emptyDomain exists, no recordIs the A, AAAA or MX record added

Caching after the fix

Resolvers cache positive answers for the record's TTL and negative answers for the SOA minimum TTL, so an error can linger after you fix it. Clear your local cache on Windows with ipconfig /flushdns; ISP caches clear on their own. If your domain is at sayt.uz, the zone is visible in the cabinet's DNS section, and sending these command outputs to support speeds up diagnosis.

Related articles

⏳ The 60-Day Domain Transfer Lock: When It Applies and How to Plan 🪪 .uz domain contact and passport verification: why it matters 📮 The SPF 10-lookup limit: why permerror happens and how to fix it 🌱 When Does a New Domain Start Showing Up in Google? Indexing and the "Sandbox"
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓