# What does a CNAME record do, and why can it conflict with other records?

Canonical URL: https://help.iagenify.com/faqs/domains/what-does-a-cname-record-do-and-why-can-it-conflict-with-other-records

[← Back to Domains FAQs](https://help.iagenify.com/faqs/domains)

HELP CENTER · FAQ Domains 2 min read
# What does a CNAME record do, and why can it conflict with other records?
A CNAME makes one DNS name an alias of another name, so resolvers follow the target to obtain its address data. DNS rules generally do not allow other record types to coexist at the same owner name, which is why adding a CNAME can conflict with existing mail, verification, or address records.
IaGenify
Domains

## Use aliases at the right name
Check whether the hostname already has A, AAAA, MX, TXT, or other records before adding a CNAME. If those records are required, use a different hostname or a provider-supported flattening feature where appropriate, understanding that flattening is not the same DNS record behavior.
A CNAME target should be a hostname, not an IP address, and chains of aliases can complicate resolution. Review provider guidance for apex-domain behavior because standards and implementations differ in what they support there.
## Verify the resulting answers
Query the authoritative zone and several recursive resolvers after a change. Confirm the alias resolves to the intended target and that required records for related names remain available.
Document why the alias exists and which service owns its target. Before changing the target, check its effect on certificates, application routing, and any integrations that rely on the hostname. [← Back to Domains FAQs](https://help.iagenify.com/faqs/domains)