Topic lessonTopic: Route 53 and ACM: names and HTTPS
Route 53 Alias vs CNAME: apex records, targets and TTLs
Alias and CNAME differ in both behavior and where they can be used. Route 53 Alias is an extension for eligible AWS resources or compatible records in the same zone. Compare example.com and www.example.com by name position, target and record type.
Explain apex constraints, Alias target/type rules, TTL behavior and the distinction from HTTP redirects.
The apex is the top name of a zone: example.com in the example.com zone. A holds IPv4 addresses, AAAA holds IPv6 addresses, and CNAME references another DNS name. No records are created here.
Similar names, different DNS answers
| Question | Alias | CNAME |
|---|---|---|
| Mechanism | Alias target configured on a record such as A/AAAA | A record type returning another DNS name |
| Zone apex | Available when target/type conditions are met | Not allowed |
| Target | Supported AWS resources or same-type records in the same zone | Another DNS name |
| Answer | Applicable A/AAAA or other target value | A name reference followed by further resolution |
| TTL | AWS target default, or referenced record’s TTL | TTL configured for the CNAME itself |
Alias is not a standalone DNS record type. An A Alias yields the applicable IPv4 answer. It does not allow an arbitrary external hostname to be used as a target.
Check apex and subdomain requirements separately
- example.com → Eligible AWS targetChoose a compatible A/AAAA Alias or other eligible type
- www.example.com → Another DNS nameReference when using CNAME
- example.com
- The zone apex
- Eligible AWS target
- For example, CloudFront
- www.example.com
- A name below the apex
- Another DNS name
- Name referenced by a CNAME
| Requirement | Decision | Reason |
|---|---|---|
| example.com → eligible CloudFront target | Consider a compatible A/AAAA Alias | CNAME is unavailable at the apex; verify target support too. |
| www.example.com → provider-specified external name | Consider the provider’s required CNAME | An arbitrary external name is not an Alias target. |
| example.com → a CNAME at www in the same zone | An apex Alias to that CNAME is not a solution | Same-zone Alias references require matching types; an apex CNAME is also invalid. |
Locate the source of the TTL
For an eligible AWS resource, Alias uses the resource’s default TTL rather than an arbitrary Alias-side value. For a record in the same zone, it uses that target record’s TTL. A CNAME and its target’s answer can be cached separately.
| Setting | Value | Result |
|---|---|---|
| blue.example.com A | 192.0.2.44 / TTL 90 seconds | Target record; documentation-only IP. |
| reports.example.com A Alias | Target=blue.example.com A | Alias uses 90 seconds, not an independent 10 seconds. |
A DNS reference does not rewrite a URL path
A CNAME from www.example.com does not send an HTTP 301/302 redirect. The requested hostname remains in the URL, so the service alias and certificate must cover it. Moving /old to /new is not a DNS-record operation.
- Identify apex versus a subordinate name.
- Check the service’s required hostname and supported connection method.
- For Alias, verify target, record type and same-zone conditions.
- Identify the TTL source and distinguish DNS from content caching.
- Verify custom-domain/certificate settings and any HTTP redirect separately.
Choose from the name and target
Choose an option to see the result and explanation.
Check, then explain in your own words
- Separate A1 name and target requirements.
- Explain A2’s 90-second result.
- Distinguish DNS and content TTLs.
- Separate HTTP redirects from DNS references.
Check your understanding: What comes first when choosing Alias or CNAME?
Check apex placement, target support and record-type compatibility.
Similar terminology does not imply identical placement and target rules.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsAlias targets, apex, record type and TTL; not an HTTP redirect. Documentation review, not live AWS verification.
Used in this lessonSimilar names, different DNS answers Check apex and subdomain requirements separately Locate the source of the TTL A DNS reference does not rewrite a URL path Choose from the name and target
Scope and conditionsRoles of A, AAAA, CNAME, NS and SOA records. Documentation review, not live AWS verification.
Used in this lessonSimilar names, different DNS answers Locate the source of the TTL Choose from the name and target
Scope and conditionsDNS target, distribution alias and certificate SAN are separate checks; certificate wildcard scope. Documentation review, not live AWS verification.
Used in this lessonA DNS reference does not rewrite a URL path