What Is a DNS CNAME Record?
A CNAME record makes one DNS name an alias of another name. A resolver follows the target name to find the relevant answer. Email providers commonly request CNAME records for supported features such as custom tracking or delegated authentication records; the required hostname and target are provider-specific.
By LeadHaste Editorial · AI-assisted editorial review ·
Follow the target, not a guessed address
For a conceptual example, track.example.com can alias a hostname supplied by a tracking provider. The target is a domain name rather than an address copied from a temporary lookup. Following the provider's documented target lets the provider manage its service addresses without requiring you to copy each subsequent address change.
Record the complete source name, record type and destination. A control panel may add the zone name automatically, so inspect the resulting fully qualified name instead of assuming the field label describes the final record. A correctly typed target under the wrong hostname will not satisfy the integration's expected lookup.
An alias is not an HTTP redirect
CNAME affects DNS resolution. It does not itself issue a browser redirect, rewrite a URL path, configure an application or create a mailbox. If the feature also needs domain verification or certificate provisioning, a successful DNS lookup is only one step in that service's documented activation process.
Traditional DNS rules restrict a CNAME name from holding other ordinary record data at the same name. Some DNS products offer flattening or alias-like features with different behavior. Follow the provider's supported configuration for the exact feature rather than substituting a similarly named control-panel option without checking how it resolves.
Verify the feature after DNS
Inspect the authoritative answer and the alias chain, then check the receiving provider's verification state. For a tracking feature, use a controlled message to inspect the actual generated hostname and destination. For an authentication feature, examine a real message and its receiver-reported result rather than relying solely on a DNS badge.
Keep the service and DNS owners identifiable. If the integration is retired, review whether the alias should also be removed to avoid leaving a hostname pointing at an unmanaged service. Record the reason and readback for any change so another operator can distinguish an intentional configuration from an obsolete record left behind.
Sources
Useful next steps
Related terms
Put the pieces into a system you own.
Explore your ICP and campaign fit on a free discovery call, then decide what your outbound operation needs.
Book your free ICP review →