Topic lessonTopic: Audit coverage and recovery design
Route 53 health checks and DNS failover: from lookup to business recovery
Check the DNS answer, the connection and the outcome separately. Trace health checks, cached answers and an actual submission in one fictional incident.
Relate health checks, failover records, recursive resolvers and a business validation to distinct observations.
This example assumes a fictional public HTTP service. No actual DNS or application changes are involved.
Trace the decision from the health check to the client
Route 53 can use health checks for specified resources, other health checks or CloudWatch alarms. In a DNS failover setup, health status can influence record selection.
- East health → Authoritative DNSSelect a record
- Authoritative DNS → Recursive resolverObserve the resolver
- Recursive resolver → Business checkTest the transaction
- East health
- Monitoring URL response
- Authoritative DNS
- Answers change to West
- Recursive resolver
- A prior answer may persist
- Business check
- Connect to West and submit
Seeing a West DNS answer and completing a West write
| Measurement | Result | What it establishes |
|---|---|---|
| 10:02 Authoritative DNS | West | Authoritative response changed |
| 10:02 Site A resolver | East | Site A still has the old response |
| 10:03 Lookup from site B | West | Site B obtained a West address |
| 10:04 Submit and read back in West | Failed | Business service remains unavailable |
Resolvers can cache answers based on TTL. Earlier answers and open connections may persist after the authoritative answering service changes its response.
Find where the chain stops
Check what the monitor measures. Compare the configured path and timestamps with the transaction test. Record which dependencies the monitoring path actually exercises.
Measure answers separately. Record authoritative response, recursive response and the destination of an actual connection, per site and time.
Define when to reopen. Pair a representative submission with read-back. Use a valid transaction, in addition to the monitoring URL, as evidence of recovery.
Check your decision
Choose an option to see the result and explanation.
Check, then explain in your own words
- Read what the health check measures.
- Observe authoritative, recursive and actual destinations.
- Verify the required transaction before reopening.
Check your understanding: Does an authoritative West response prove recovery?
Check where users connect and whether the business transaction completes.
DNS is only one step in the failover.
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 conditionsHealth-check targets and DNS failover.
Used in this lessonTrace the decision from the health check to the client Find where the chain stops
Scope and conditionsFailover records, health and TTL configuration.
Used in this lessonSeeing a West DNS answer and completing a West write Find where the chain stops