The domain’s registration names a nameserver that does not actually serve the domain — it answers REFUSED, answers without authority, or does not answer at all. Old servers left in the list after a move are the usual reason. Resolvers skip them if they can; if every listed server is lame, the domain fails.
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 4242
How 5 other clients word the same error
nslookup
** server can't find example.com: REFUSED
Google Public DNS
; EDE: 0 (Other Error): ([192.0.2.1] Lame delegation at example.com for www.example.com/a)
Extended error
; EDE: 20 (Not Authoritative)
Windows nslookup
*** dns.example can't find example.com: Query refused
Node.js
Error: queryA EREFUSED example.com
| Error | REFUSED |
| Usually fixed by | The domain owner |
| RCODE | 5 — Query Refused (RFC 1035) |
| Term | “Lame delegation” — RFC 9499 calls it historic, with several meanings |
| Usual cause | An old nameserver still listed after a move |
Check the domain’s nameservers
Enter the domain: we find its nameservers and ask each one whether it answers for the domain.
What it means
An authoritative server answers REFUSED for a zone it does not host. When the registrar’s nameserver list includes such a server, the delegation is “lame”: resolvers that ask it get REFUSED, a non-authoritative answer or silence, and have to try another. A resolver may also refuse clients it does not serve, which is a different REFUSED.
Why it happens
- An old DNS host’s nameservers left in the list at the registrar after moving.
- The zone deleted at the DNS host while the registrar still points there.
- A typo in a nameserver name at the registrar.
- Querying a resolver that only serves its own network — REFUSED to outsiders is normal there.
How to fix it
- Find which listed nameserver is lame with the check above, or by asking each one directly.
- At the registrar, list only the nameservers of the DNS host that actually holds the zone.
- Or add the zone to the server that is listed but not serving it.
See it for yourself
dig example.com NS +short
dig example.com SOA @ns1.example-dns.net +norecurse
Ask each listed nameserver for the SOA: every one should answer with the aa flag set. REFUSED or no answer marks the lame one.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 9499 — rfc-editor.org
- RFC 9520 — rfc-editor.org
- RFC 8906 — rfc-editor.org
- Domain Troubleshooting — developers.google.com