Topic lessonTopic: Route 53 and ACM: names and HTTPS
What is Amazon Route 53? Hosted zones, delegation and DNS records
Route 53 manages DNS answers. Domain registration, DNS configuration and health checks are separate functions; you need not use all of them together. Follow a public-site name to understand where queries go and which hosted-zone settings apply.
Distinguish registration, authoritative DNS and resolvers, then check zone visibility and delegation.
DNS looks up information associated with a name. An authoritative server supplies its zone’s answers; a resolver performs lookups for a client. This lesson registers or transfers no domain.
Separate domain registration from DNS answers
| Role | Responsibility | Configuration to inspect |
|---|---|---|
| Registrar | Manage domain registration | Delegated name servers. |
| Authoritative DNS | Answer records for its zone | Route 53 hosted zone and records. |
| Resolver | Perform and cache lookups for clients | Query context, resolver and remaining TTL. |
A hosted zone groups DNS information for a domain and its descendants. Creating one does not automatically direct public queries to it. The parent-side delegation must match the name servers assigned to the intended zone.
Identify the zone that is actually delegated
- Parent delegation → Public hosted zoneAlign the delegated name servers
- Resolver → Public hosted zoneQuery when lookup/cache conditions require it
- Public hosted zone → Zone recordsUse this zone’s configured answers
- Parent delegation
- Names the intended zone’s NS
- Public hosted zone
- Assigned NS answer the queries
- Resolver
- Performs required lookups
- Zone records
- Manage name, type and value
| Setting | Zone A | Zone B |
|---|---|---|
| Zone name | example.com | example.com |
| Public delegation | Points to A’s assigned NS | Not delegated to B |
| New reports record | Not added | Added |
In R1, first reconcile delegation with the zone being edited. Adding a record in B does not change answers from A. Do not immediately switch delegation: review existing mail and other records in A and establish authorized change ownership.
Public and private zones have different query contexts
| Type | Use | Additional check |
|---|---|---|
| Public hosted zone | Internet-facing names | Parent delegation and public records. |
| Private hosted zone | Resolution within associated VPC contexts | VPC associations, DNS attributes and resolver conditions. |
Associated private zones and resolver rules affect answers in a VPC. Internal DNS visibility is distinct from network restrictions and authentication at the destination. Lack of public DNS visibility alone is not a security verdict.
Separate record type from answer-selection policy
| Type | Content | Distinction |
|---|---|---|
| A / AAAA | IPv4 / IPv6 addresses | Not an HTTP URL or path. |
| CNAME | A reference to another DNS name | Not an HTTP redirect; unavailable at the zone apex. |
| NS | Authoritative name servers | Not the web server’s IP address. |
| Alias | Route 53 extension referencing an eligible target | Not a separate wire-level DNS record type named Alias. |
Route 53 offers DNS answer selection such as weighted, latency and failover policies. DNS answers are cached; this is not a device that moves established connections immediately. Whether to add health checks is a separate design choice based on the requirement and target.
- Fix the name, type and query source.
- Distinguish public and VPC-local resolution.
- For public DNS, compare parent delegation with assigned zone NS.
- Inspect the intended zone’s record and value.
- Investigate prior TTLs and caches for old answers.
- Verify TLS and HTTP separately after DNS.
Check delegation and records
Choose an option to see the result and explanation.
Check, then explain in your own words
- Separate registration, authority and resolution.
- Explain R1’s two zones and active delegation.
- Identify public versus private query contexts.
- Distinguish A/AAAA, CNAME, NS and Alias.
Check your understanding: What should you correlate when a record exists but the name does not resolve?
The query source, DNS view, delegation and edited zone.
A stored record and a query using that zone are different facts.
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.
- Amazon Route 53 overviewChecked:
Scope and conditionsRegistration, DNS answers and health checks are separate features; resolver versus authoritative DNS. Documentation review, not live AWS verification.
Used in this lessonSeparate domain registration from DNS answers Separate record type from answer-selection policy
Scope and conditionsDelegation, duplicate zones and prior TTLs; lowering TTL does not immediately remove existing cache entries. Documentation review, not live AWS verification.
Used in this lessonSeparate domain registration from DNS answers Separate record type from answer-selection policy Check delegation and records
- Route 53: NS and SOA recordsChecked:
Scope and conditionsNegative caching for NXDOMAIN/NODATA uses the smaller of SOA TTL and MINIMUM. Documentation review, not live AWS verification.
Used in this lessonSeparate domain registration from DNS answers
- Route 53: Check DNS responsesChecked:
Scope and conditionsTest record evaluates hosted-zone configuration; it does not verify live public delegation. Documentation review, not live AWS verification.
Used in this lessonIdentify the zone that is actually delegated Check delegation and records
Scope and conditionsVPC association, matching namespaces and no automatic public-DNS fallback for an absent private record. Documentation review, not live AWS verification.
Used in this lessonPublic and private zones have different query contexts Check delegation and records
Scope and conditionsRoles of A, AAAA, CNAME, NS and SOA records. Documentation review, not live AWS verification.
Used in this lessonSeparate record type from answer-selection policy
Scope and conditionsAlias targets, apex, record type and TTL; not an HTTP redirect. Documentation review, not live AWS verification.
Used in this lessonSeparate record type from answer-selection policy