Topic lessonTopic: Route 53 and ACM: names and HTTPS
Route 53 DNS troubleshooting: delegation, records and cached answers
A record existing in Route 53 does not prove a particular query can resolve it. Check delegation, the edited zone, record type, public versus VPC context and cached prior answers. Also distinguish DNS failure from later HTTPS or HTTP failures.
Distinguish delegation mismatches, private-zone effects and negative caching, then choose a safe next check.
A queries IPv4 information; AAAA queries IPv6. NS identifies a zone’s authority and TTL governs answer reuse. All observations are fictional; no system DNS settings or live queries are changed.
Record the query conditions and response
| Item | Example | Purpose |
|---|---|---|
| Exact name/type | reports.example.com / A | Do not mix with AAAA or another name. |
| Query source | External client / associated VPC | Distinguish public and private views. |
| DNS server queried | Configured resolver / intended authoritative NS | Separate cached and authoritative answers. |
| Time/result | NXDOMAIN, answer value and remaining TTL | Do not mix unrelated before/after queries. |
NXDOMAIN is a negative answer for a nonexistent name; NODATA indicates that the name exists but the requested type has no record. Negative answers can be cached. If an address is returned and TLS subsequently fails, that is a different observation from a missing DNS record.
For public DNS, identify the intended authoritative zone
- Fix name and type → Public DNS checksAn internet-side query
- Fix name and type → VPC DNS checksA query through the VPC resolver
- Fix name and type
- Example: reports.example.com A
- Public DNS checks
- Delegated NS and intended zone
- VPC DNS checks
- Association and matching private zone
Name/type: reports.example.com A
Parent delegation: assigned NS of hosted zone A
Zone A: no reports record
Zone B: reports A 192.0.2.44
Test record in B: expected A answer
Public authoritative answer from A: NXDOMAIND1 delegates to A while only B was edited. Test record in B evaluates B’s configuration, not whether public DNS uses B. Reconcile delegation and edit ownership before changing anything, including existing mail or other records.
- Compare parent delegation with the intended zone’s assigned NS.
- Identify the active zone when duplicate names exist.
- Check name, type and value in that zone.
- Compare authoritative and resolver observations for the same query conditions.
- Distinguish cached NS, record and negative-answer lifetimes.
Trace a negative answer retained after record creation
For Route 53 public-zone negative answers, the cache lifetime uses the smaller of the SOA record TTL and its MINIMUM field. SOA holds zone metadata. A newly created A record’s TTL does not describe an already cached “does not exist” answer.
| Time | Event | Result under N1 |
|---|---|---|
| 0 s | Authoritative NXDOMAIN; SOA TTL 900 / MINIMUM 300 | Retain a negative answer for 300 seconds. |
| 60 s | A record added to the intended zone | Authority changes; the prior negative cache is not erased. |
| 120 s | Same name queried through the same resolver | Reuse the negative entry under these assumptions. |
| 301 s | After expiry, authority is queried and returns A | Return the new address under the stated conditions. |
A matching private zone does not automatically fall back to public DNS
| Setting | Content |
|---|---|
| Public example.com zone | www.example.com A exists |
| Associated private example.com zone | No matching www name/type record |
| www A query through VPC Resolver | Uses the matching private zone; NXDOMAIN rather than public fallback |
Recreating the public record does not repair P1’s selected private-zone gap. Inspect VPC association, the most specific matching namespace, records and resolver rules. Do not publish internal DNS data as a shortcut.
Choose a check supported by the observations
Choose an option to see the result and explanation.
Check, then explain in your own words
- Reconcile D1 delegation A and edited zone B.
- Distinguish NXDOMAIN from NODATA.
- Derive N1’s 300 seconds from the SOA values.
- Explain P1’s lack of public fallback.
- Check TLS and HTTP separately after DNS.
Check your understanding: What should precede a diagnosis of propagation delay?
Name/type, query source, delegation, selected zone and response kind.
Waiting does not repair an edited wrong zone or missing private record.
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.
- 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 lessonRecord the query conditions and response Trace a negative answer retained after record creation Choose a check supported by the observations
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 lessonFor public DNS, identify the intended authoritative zone Trace a negative answer retained after record creation Choose a check supported by the observations
- 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 lessonFor public DNS, identify the intended authoritative zone Choose a check supported by the observations
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 lessonA matching private zone does not automatically fall back to public DNS Choose a check supported by the observations