CNAME and other data
A CNAME cannot share a name with other records
Seen in BIND (named-checkzone, zone load), Route 53, Cloudflare (error 81053)
The zone has a CNAME on a name that also has other records, which DNS does not allow.
Common causes
- A CNAME was added at the zone apex, which always has SOA and NS records.
- A name already has A, MX or TXT records and someone added a CNAME for it, or the reverse.
- A leftover record from an imported zone conflicts with a new CNAME.
How to fix it
- Remove the other records on that name, or use A/AAAA records instead of the CNAME.
- At the apex, use your provider's alias or CNAME-flattening feature (ALIAS, ANAME, Route 53 alias) instead of a CNAME.
- Validate BIND zones with `named-checkzone example.com /path/to/zonefile` before reloading.
Got a different message? Paste it into the error explainer.
Related errors
- DNS_PROBE_FINISHED_NXDOMAIN · The domain name doesn't exist
- SERVFAIL · The DNS server failed to answer
- REFUSED · The DNS server refused the query
- ERR_NAME_NOT_RESOLVED · The browser couldn't resolve the hostname
- DNS_PROBE_FINISHED_BAD_CONFIG · The configured DNS server is not working
- ** server can't find example.com: NXDOMAIN · nslookup says the name doesn't exist
- *** UnKnown can't find · nslookup couldn't name the DNS server, then the lookup failed
- Non-authoritative answer: · The answer came from a resolver cache, which is normal
- ;; connection timed out; no servers could be reached · No DNS server answered the query
- status: NOERROR, ANSWER: 0 · The name exists but has no record of that type
- FORMERR · The DNS server could not parse the query
- NOTIMP · The DNS server does not support that kind of query