Choose a CNAME or a Route 53 alias according to the name and target you need. They are not interchangeable: a CNAME cannot sit at the zone apex, while Route 53 supports certain alias targets there.

Add a subdomain CNAME

1. Open the intended Route 53 zone’s records in the module.
2. Search for the name and check for existing records.
3. Choose CNAME and enter the subdomain name, TTL and target hostname.
4. Save, then reload and confirm the resulting record.
5. Check authoritative DNS and the destination service separately.

Use a hostname as the target, not a full URL with a protocol or page path. A CNAME cannot coexist with other ordinary record types at the same name. Do not replace a working mail or verification name without reviewing what already uses it.

Use the module’s same-zone alias case

The module’s released ALIAS workflow writes an IPv4 A alias. For a target record in the same hosted zone, choose an existing ordinary A record with the intended address and use that record’s hostname as the alias target. Select ALIAS, enter the alias name and target, save, then verify that public answers match the intended target.

This can address a root-domain requirement where a CNAME would be invalid. Do not target another CNAME for an apex alias. Review the target name and its address before publishing an alias that depends on it.

Keep advanced AWS aliases separate

AWS supports additional alias cases, but this module workflow is not a complete AWS resource picker. Do not assume entering any CloudFront, load-balancer or S3 hostname is enough: the correct AWS target hosted-zone identity and record type also matter. Use the appropriate AWS procedure for a resource alias that the module form does not fully describe.

AWS’s alias versus CNAME guide explains the service-level distinction. An alias is DNS routing, not a website redirect; the target must still serve the requested hostname and its HTTPS certificate.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

See the PD AWS Route 53 DNS Blesta guide for related tasks, or explore the module.