The name exists, but not the kind of record you asked for — no A record for the address, no MX for mail, no TXT for the check. DNS answers “no error” with nothing in it. The fix is to add the record the service needs.
*** Can't find example.com: No answer
How 5 other clients word the same error
host
example.com has no MX record
dig
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4242 … ANSWER: 0
Linux (ping, Python)
No address associated with hostname · [Errno -5] No address associated with hostname
Node.js
Error: queryMx ENODATA example.com
systemd-resolved
resolve call failed: 'example.com' does not have any RR of the requested type
| Error | No answer (NODATA) |
| Usually fixed by | The domain owner |
| RCODE | 0 — NOERROR, with an empty answer (RFC 2308 calls it NODATA) |
| Not the same as | NXDOMAIN — here the name exists |
| Windows | Often reports it as “No such host is known”, like NXDOMAIN |
Look up one record
Enter the name and choose the type: one question to DNS, answered as it is — including “no such name” and “no record of that type”.
What it means
NXDOMAIN says the name does not exist; NODATA says it exists but has no record of the requested type. dig shows status: NOERROR with ANSWER: 0, nslookup says “No answer”, and Linux programs report “No address associated with hostname”. Resolvers cache this “nothing here” answer for the zone’s negative TTL, like NXDOMAIN.
A name that does not exist at all can look the same. DNS hosts that use compact denial of existence for DNSSEC (RFC 9824) — Cloudflare among them — answer a missing name with no error and no records rather than NXDOMAIN, so check the name is spelled as the zone has it before adding a record.
Why it happens
- The record was never added — an MX for mail, a TXT for verification, an AAAA for IPv6.
- The record was added under a slightly different name.
- Only IPv6 or only IPv4 is published, and the client asks for the other.
How to fix it
- Look up the name and type with the check above.
- Add the record at the DNS host, with the name exactly as the service gives it — see our DNS host guides for what to type.
- Allow for the negative TTL before re-checking.
See it for yourself
dig example.com MX @1.1.1.1
status: NOERROR with ANSWER: 0 is NODATA; status: NXDOMAIN means the name itself is missing.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 2308 — rfc-editor.org
- RFC 9824 — rfc-editor.org
- glibc source: resolv/netdb.h — sourceware.org
- DNS — Node.js v26.10.0 Documentation — nodejs.org
- nslookup — learn.microsoft.com