What is Amazon Route 53 and how does it handle DNS?
What is Amazon Route 53? Learn how it handles DNS resolution, hosted zones, alias records, health checks, and routing policies like latency and failover.
Expected Interview Answer
Amazon Route 53 is AWS's highly available, scalable Domain Name System (DNS) web service that translates human-readable domain names into IP addresses and routes end-user traffic to the right endpoint.
Route 53 stores DNS records in hosted zones and answers queries from a global network of authoritative name servers. Beyond basic resolution it supports domain registration, health checks, and advanced routing policies — simple, weighted, latency-based, failover, geolocation, geoproximity, and multivalue answer — so it can steer users to the fastest or healthiest endpoint. Alias records let you point a zone apex directly at AWS resources like an ELB, CloudFront, or S3 website without an extra CNAME hop.
- Highly available and globally distributed DNS resolution
- Multiple routing policies for latency, failover, and geolocation
- Health checks reroute traffic away from unhealthy endpoints
- Alias records map the zone apex to AWS resources for free
- Integrated domain registration and DNS management
AI Mentor Explanation
Route 53 is like a match's control room that turns a fan's request for 'the India game' into the exact stadium and gate to enter. Its routing policies work like directing supporters to the nearest turnstile with the shortest queue, and its health checks are stewards who reroute the crowd instantly if one gate jams, keeping everyone flowing to a working entrance.
Step-by-Step Explanation
Step 1
Register or import a domain
Buy a domain in Route 53 or point an existing domain's name servers to a Route 53 hosted zone.
Step 2
Create a hosted zone
The hosted zone holds all DNS records (A, AAAA, CNAME, MX, TXT, alias) for your domain.
Step 3
Add records
Create records that map names to IPs or AWS resources; use alias records for the zone apex.
Step 4
Choose a routing policy
Select simple, weighted, latency, failover, geolocation, geoproximity, or multivalue to control traffic.
Step 5
Attach health checks
Associate health checks so Route 53 stops returning endpoints that are failing.
What Interviewer Expects
- Route 53 defined as a managed authoritative DNS service
- Understanding of hosted zones and record types
- Knowledge of routing policies (latency, failover, weighted, geolocation)
- Awareness of health checks and automatic failover
- Alias records vs CNAME and zone-apex support
Common Mistakes
- Calling Route 53 only a domain registrar and ignoring routing policies
- Using a CNAME at the zone apex instead of an alias record
- Confusing latency-based routing with geolocation routing
- Assuming health checks are automatic without configuring them
- Thinking Route 53 is a Region-scoped service rather than global
Best Answer (HR Friendly)
“Route 53 is Amazon's phone book for the internet: it turns a website name people type into the numeric address computers use, and sends visitors to the nearest or healthiest server. It can also register domain names and automatically reroute traffic if a server goes down.”
Code Example
{
"Comment": "Route users to the lowest-latency ELB",
"Changes": [
{
"Action": "UPSERT",
"ResourceRecordSet": {
"Name": "app.example.com",
"Type": "A",
"SetIdentifier": "us-east-1",
"Region": "us-east-1",
"AliasTarget": {
"HostedZoneId": "Z35SXDOTRQ7X7K",
"DNSName": "my-elb-123.us-east-1.elb.amazonaws.com",
"EvaluateTargetHealth": true
}
}
}
]
}Follow-up Questions
- When would you use an alias record instead of a CNAME?
- How does latency-based routing differ from geolocation routing?
- How do Route 53 health checks trigger failover?
- What is the purpose of a private hosted zone?
- How would you design an active-passive multi-Region failover with Route 53?
MCQ Practice
1. What is the primary function of Amazon Route 53?
Route 53 is a managed, highly available DNS service that resolves domain names and routes traffic using various policies.
2. Which record type lets you point a zone apex directly at an AWS resource?
Alias records can map the zone apex to AWS resources like an ELB or CloudFront, which a CNAME cannot do at the apex.
3. Which routing policy sends users to the endpoint with the lowest network latency?
Latency-based routing directs each user to the Region that gives them the lowest latency.
Flash Cards
Amazon Route 53 — A highly available managed DNS service that resolves domain names and routes traffic.
Hosted zone — A container in Route 53 holding all DNS records for a domain.
Alias record — Maps the zone apex to AWS resources (ELB, CloudFront, S3) without a CNAME hop.
Failover routing — Uses health checks to send traffic to a standby endpoint when the primary is unhealthy.