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

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.

What you will learn

Distinguish registration, authoritative DNS and resolvers, then check zone visibility and delegation.

Prerequisite

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

Separate roles even when one provider offers them
RoleResponsibilityConfiguration to inspect
RegistrarManage domain registrationDelegated name servers.
Authoritative DNSAnswer records for its zoneRoute 53 hosted zone and records.
ResolverPerform and cache lookups for clientsQuery 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

DNS configuration relationships, not the web-content path
DNS configuration relationships, not the web-content path1: Parent delegation — Align the delegated name servers — Public hosted zone. 2: Resolver — Query when lookup/cache conditions require it — Public hosted zone. 3: Public hosted zone — Use this zone’s configured answers — Zone records123Parent delegationPublic hosted zoneResolverZone recordsDNS configuration relationships, not the web-content path1: Parent delegation — Align the delegated name servers — Public hosted zone. 2: Resolver — Query when lookup/cache conditions require it — Public hosted zone. 3: Public hosted zone — Use this zone’s configured answers — Zone records123ParentdelegationPublic hostedzoneResolverZone records
  1. Parent delegation → Public hosted zoneAlign the delegated name servers
  2. Resolver → Public hosted zoneQuery when lookup/cache conditions require it
  3. 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
R1: two hosted zones with the same name
SettingZone AZone B
Zone nameexample.comexample.com
Public delegationPoints to A’s assigned NSNot delegated to B
New reports recordNot addedAdded

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

The same name can use different DNS views
TypeUseAdditional check
Public hosted zoneInternet-facing namesParent delegation and public records.
Private hosted zoneResolution within associated VPC contextsVPC 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

Core DNS record distinctions
TypeContentDistinction
A / AAAAIPv4 / IPv6 addressesNot an HTTP URL or path.
CNAMEA reference to another DNS nameNot an HTTP redirect; unavailable at the zone apex.
NSAuthoritative name serversNot the web server’s IP address.
AliasRoute 53 extension referencing an eligible targetNot 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.

  1. Fix the name, type and query source.
  2. Distinguish public and VPC-local resolution.
  3. For public DNS, compare parent delegation with assigned zone NS.
  4. Inspect the intended zone’s record and value.
  5. Investigate prior TTLs and caches for old answers.
  6. Verify TLS and HTTP separately after DNS.

Check delegation and records

Choose an option to see the result and explanation.

Does adding a record only in R1 zone B change the public answer?
Read the answer and reason

Answer: Not established; delegation points to A · Reconcile the edited zone with the delegated one.

What still needs checking after Test record succeeds?
Read the answer and reason

Answer: Public delegation and actual resolution · The tool evaluates the zone configuration, not the live public delegation path.

Does a private DNS name remove the need for destination access controls?
Read the answer and reason

Answer: No; resolution and access control are separate · Design destination networking, authentication and authorization separately.

Check, then explain in your own words

  1. Separate registration, authority and resolution.
  2. Explain R1’s two zones and active delegation.
  3. Identify public versus private query contexts.
  4. 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.