What Is Amazon Route 53 and How Does It Work?
Learn what Amazon Route 53 is, how its DNS resolution works, its routing policies, and how health checks power automatic failover across regions.
Expected Interview Answer
Amazon Route 53 is AWS's highly available, scalable DNS web service that translates domain names into IP addresses, and it also supports domain registration and health-check-based traffic routing.
Route 53 answers DNS queries for your domain from a global network of authoritative name servers, so users resolve names like example.com to the correct resource. Beyond simple resolution, it supports routing policies such as weighted (split traffic by percentage), latency-based (route to the lowest-latency region), geolocation, and failover (route to a backup if health checks fail), which let you build multi-region architectures with automatic failover. It integrates directly with other AWS resources through alias records, letting you point a domain straight at a load balancer, CloudFront distribution, or S3 website endpoint without an extra hop, and it offers a 100% availability SLA.
- Resolves domain names reliably with a global anycast DNS network
- Supports multiple routing policies for latency, geography, and failover
- Integrates natively with AWS resources via alias records
- Provides health checks that automatically reroute traffic from unhealthy endpoints
- Can also register and manage domain names directly
AI Mentor Explanation
Route 53 is like the stadium announcer system that tells every fan exactly which gate and stand corresponds to their ticket, no matter which entrance they approach from. If one stand's turnstiles jam, the announcer redirects incoming fans to an open stand automatically, and for a doubleheader across two grounds it can send fans to whichever ground is currently less crowded.
Step-by-Step Explanation
Step 1
Register or point a domain
Route 53 can register a new domain or serve as the authoritative DNS for a domain registered elsewhere.
Step 2
Create a hosted zone
A hosted zone stores DNS records (A, CNAME, MX, and alias records) for the domain.
Step 3
Choose a routing policy
Simple, weighted, latency-based, geolocation, or failover policies determine which record answers each query.
Step 4
Attach health checks
Route 53 can monitor endpoint health and stop routing traffic to unhealthy targets automatically.
Step 5
Use alias records for AWS resources
Alias records point directly at ELB, CloudFront, or S3 endpoints without an extra DNS lookup.
What Interviewer Expects
- Explains Route 53 as DNS plus domain registration and traffic routing
- Names multiple routing policies (weighted, latency, geolocation, failover)
- Describes health checks driving automatic failover
- Mentions alias records for integrating with AWS-native endpoints
- Knows Route 53 offers a 100% availability SLA
Common Mistakes
- Thinking Route 53 is only a domain registrar
- Forgetting that alias records avoid extra DNS lookups compared to CNAMEs at the zone apex
- Assuming failover routing works without configuring health checks
- Confusing latency-based routing with geolocation routing
Best Answer (HR Friendly)
“Route 53 is Amazon's DNS service — it's what translates a website address you type into the actual server that responds. It can also register domains and, if one server or region goes down, automatically send visitors to a healthy backup instead.”
Code Example
resource "aws_route53_record" "app" {
zone_id = aws_route53_zone.primary.zone_id
name = "app.example.com"
type = "A"
alias {
name = aws_lb.app.dns_name
zone_id = aws_lb.app.zone_id
evaluate_target_health = true
}
failover_routing_policy {
type = "PRIMARY"
}
set_identifier = "primary"
health_check_id = aws_route53_health_check.app.id
}Follow-up Questions
- What's the difference between an alias record and a CNAME record?
- How does latency-based routing decide which endpoint to return?
- How do Route 53 health checks trigger failover?
- What is a hosted zone and how does it relate to a domain?
- How would you implement a blue/green deployment using weighted routing?
MCQ Practice
1. What is Amazon Route 53 primarily used for?
Route 53 is AWS's DNS web service, also supporting domain registration and traffic routing policies.
2. Which routing policy sends traffic to the region with the lowest response time?
Latency-based routing directs users to the AWS region that provides the lowest latency for them.
3. What benefit does an alias record provide over a standard CNAME at the zone apex?
Alias records let you map a domain, including the apex, directly to AWS resources like an ELB or CloudFront distribution.
Flash Cards
What is Route 53? — AWS's scalable DNS web service, also supporting domain registration and traffic routing.
Name three Route 53 routing policies. — Weighted, latency-based, and failover (also geolocation and simple).
What triggers Route 53 failover routing? — Health checks detecting that the primary endpoint is unhealthy.
What is an alias record used for? — Pointing a domain, including the zone apex, directly at AWS resources like ELB or CloudFront.