INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Distinguish delegation mismatches, private-zone effects and negative caching, then choose a safe next check.

Prerequisite

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

Capture these observations first
ItemExamplePurpose
Exact name/typereports.example.com / ADo not mix with AAAA or another name.
Query sourceExternal client / associated VPCDistinguish public and private views.
DNS server queriedConfigured resolver / intended authoritative NSSeparate cached and authoritative answers.
Time/resultNXDOMAIN, answer value and remaining TTLDo 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

The query context determines which configuration to investigate
The query context determines which configuration to investigate1: Fix name and type — An internet-side query — Public DNS checks. 2: Fix name and type — A query through the VPC resolver — VPC DNS checks12Fix name and typePublic DNS checksVPC DNS checksThe query context determines which configuration to investigate1: Fix name and type — An internet-side query — Public DNS checks. 2: Fix name and type — A query through the VPC resolver — VPC DNS checks12Fix name andtypePublic DNSchecksVPC DNS checks
  1. Fix name and type → Public DNS checksAn internet-side query
  2. 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
D1: a configuration test passes while public DNS returns NXDOMAIN
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: NXDOMAIN

D1 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.

  1. Compare parent delegation with the intended zone’s assigned NS.
  2. Identify the active zone when duplicate names exist.
  3. Check name, type and value in that zone.
  4. Compare authoritative and resolver observations for the same query conditions.
  5. 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.

N1: one resolver, 300-second negative TTL, no early eviction
TimeEventResult under N1
0 sAuthoritative NXDOMAIN; SOA TTL 900 / MINIMUM 300Retain a negative answer for 300 seconds.
60 sA record added to the intended zoneAuthority changes; the prior negative cache is not erased.
120 sSame name queried through the same resolverReuse the negative entry under these assumptions.
301 sAfter expiry, authority is queried and returns AReturn the new address under the stated conditions.

A matching private zone does not automatically fall back to public DNS

P1: associated VPC, no overriding resolver rule, required DNS attributes enabled
SettingContent
Public example.com zonewww.example.com A exists
Associated private example.com zoneNo matching www name/type record
www A query through VPC ResolverUses 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.

What should D1 check when Test record passes but public resolution fails?
Read the answer and reason

Answer: Parent delegation and the edited zone · Public delegation points to A while the record was edited in B.

What does the same resolver return at 120 seconds under N1?
Read the answer and reason

Answer: The retained NXDOMAIN under the assumptions · The negative entry retained for 300 seconds at time zero is still valid.

Does P1 automatically use the public www record when the private zone lacks it?
Read the answer and reason

Answer: No; inspect the selected private zone · An absent record in the matching private zone does not trigger automatic public fallback.

Check, then explain in your own words

  1. Reconcile D1 delegation A and edited zone B.
  2. Distinguish NXDOMAIN from NODATA.
  3. Derive N1’s 300 seconds from the SOA values.
  4. Explain P1’s lack of public fallback.
  5. 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.