Topic · DNS & Infrastructure
CNAME record
A CNAME record aliases one DNS name to another canonical DNS name. It redirects DNS name resolution to a target name.
How it works
Resolvers follow the alias to retrieve the target records. Resolvers follow this alias when finding the target resource records.
What can go wrong
A CNAME cannot normally coexist with other data at the same DNS owner name.
What to check or do
Use CNAME records for vendor selectors or delegated services only when supported.
How to investigate CNAME record
- Signal to investigate
- An email verification service asks for a CNAME, but the owner name already holds another record.
- Evidence to collect
- Query the exact owner name for CNAME and other RR types on authoritative servers; inspect the provider-supplied target.
- Common wrong conclusion
- A CNAME generally cannot coexist at the same owner name with ordinary unrelated records.
How to interpret the evidence
A CNAME aliases a DNS name; it does not directly publish the target TXT value and can behave differently from a provider-specific alias feature. Avoid adding an apex CNAME without understanding provider flattening behavior.
What to change and how to verify it
Use the exact hostname required by the provider and remove conflicting RRsets only after documenting their existing purpose.
dig +short CNAME selector.example.comEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.