What Is Route 53?
Route 53 is AWS's highly available and scalable Domain Name System (DNS) web service, named after the standard port 53 that DNS uses, and it provides three main functions: domain registration, DNS record hosting through hosted zones, and health checking with sophisticated traffic routing. When you create a hosted zone for a domain like example.com, Route 53 assigns four authoritative name servers spread across different top-level domains for redundancy, and it backs this with a 100% availability SLA — the only AWS service with that guarantee, reflecting how critical DNS resolution is to virtually every other request an application handles.
Cricket analogy: Route 53 is like the ICC's official fixture and venue directory — before any match happens, every team, broadcaster, and fan needs to look up exactly which ground a game is being played at, and that directory has to be rock-solid reliable.
Record Types and Alias Records
Route 53 hosted zones support standard DNS record types including A (IPv4 address), AAAA (IPv6 address), CNAME (canonical name, aliasing one hostname to another), MX (mail routing), and TXT (arbitrary text, often used for domain verification), but it also offers a Route 53-specific extension called an alias record. Unlike a CNAME, which cannot be used at a zone apex (the bare domain like example.com without a subdomain) per DNS specification, an alias record can point a zone apex directly at an AWS resource such as a CloudFront distribution, an Application Load Balancer, or an S3 static website endpoint, and Route 53 resolves it internally without an extra DNS lookup, making it both technically legal and free of the additional latency a CNAME chain would introduce.
Cricket analogy: A CNAME is like telling a scorer 'go check what's written on the other board first,' while an alias record is like the scorer having the live score memorized directly — the alias skips the extra lookup step, resolving instantly.
Routing Policies
Beyond simple one-to-one DNS resolution, Route 53 offers several routing policies that make it a traffic management tool as much as a naming service: weighted routing splits traffic between multiple resources by assigned percentage (useful for canary deployments), latency-based routing sends users to the region with the lowest measured latency, geolocation routing sends users to specific endpoints based on their geographic location (useful for legal compliance or content localization), and failover routing automatically shifts traffic to a standby resource when a Route 53 health check detects the primary has failed. These policies can be combined hierarchically — for example, using latency-based routing at the top level to pick a region, then weighted routing within that region to canary-test a new deployment.
Cricket analogy: Weighted routing is like a captain rotating overs between two spinners at a 70/30 split based on pitch conditions, while failover routing is like an emergency third bowler coming on only if the first choice pulls a hamstring.
# Create an alias A record pointing the zone apex to a CloudFront distribution
aws route53 change-resource-record-sets \
--hosted-zone-id Z1234567890ABC \
--change-batch '{
"Changes": [{
"Action": "UPSERT",
"ResourceRecordSet": {
"Name": "example.com",
"Type": "A",
"AliasTarget": {
"HostedZoneId": "Z2FDTNDATAQYW2",
"DNSName": "d123456abcdef8.cloudfront.net",
"EvaluateTargetHealth": false
}
}
}]
}'
# Create a health check used for failover routing
aws route53 create-health-check \
--caller-reference primary-web-2026 \
--health-check-config Type=HTTPS,ResourcePath=/health,FullyQualifiedDomainName=primary.example.com,Port=443Alias records are free of charge for AWS resource queries and can be used at the zone apex, unlike CNAMEs. Always prefer an alias record over a CNAME when pointing at supported AWS resources like CloudFront, ALB, or S3 website endpoints.
Route 53 health checks used for failover routing only check endpoint health from outside the VPC by default — if your primary resource is in a private subnet with no public endpoint, the health check will report unhealthy even if the resource is functioning correctly, so you must configure a public health-check endpoint or use CloudWatch alarm-based health checks instead.
- Route 53 provides domain registration, DNS hosting, and health-check-driven traffic routing.
- Hosted zones are backed by 4 redundant name servers and a 100% availability SLA.
- Alias records can be used at the zone apex and add no extra DNS lookup latency, unlike CNAMEs.
- Weighted routing splits traffic by percentage, ideal for canary deployments.
- Latency-based routing sends users to the lowest-latency region.
- Geolocation routing enables compliance and localization based on user location.
- Failover routing shifts traffic to a standby resource when health checks detect failure.
Practice what you learned
1. Why is Route 53 the only AWS service with a 100% availability SLA?
2. Why can't a CNAME record be used at a domain's zone apex?
3. Which routing policy would you use to send 10% of traffic to a new deployment for canary testing?
4. What triggers Route 53 failover routing to switch traffic to a standby resource?
5. What advantage does an alias record have over a CNAME when pointing to a CloudFront distribution?
Was this page helpful?
You May Also Like
AWS CloudFront Basics
Understand how Amazon CloudFront's global CDN caches and accelerates content delivery, including origins, cache behaviors, and invalidation strategies.
VPC Fundamentals
Learn how Amazon VPC creates an isolated, software-defined network inside AWS, including CIDR planning, default vs custom VPCs, and connectivity options.