Route 53
Definition
AWS DNS service that routes internet traffic to your applications, ensuring high availability and low latency for users worldwide.
Use Cases
- Netflix: Highly available DNS routing for global streaming services and APIs — Uses Amazon Route 53 as authoritative DNS and applies routing policies (such as latency-based and weighted routing) to direct users to healthy, optimal endpoints across regions and infrastructure. (Improved resiliency and user experience by steering traffic away from unhealthy endpoints and toward lower-latency locations.)
- Airbnb: Reliable domain name resolution for web and API traffic — Hosts public DNS zones in Amazon Route 53 and manages DNS records for application endpoints, enabling controlled changes (e.g., cutovers and migrations) using DNS updates. (Simplified DNS operations and safer traffic transitions during infrastructure changes.)
Provider Equivalents
- AWS: Amazon Route 53
- Azure: Azure DNS
- GCP: Cloud DNS
- OCI: OCI DNS
Frequently Asked Questions
- What's the difference between Route 53 and a CDN like CloudFront?
- Route 53 is DNS: it translates a domain name (like example.com) into an IP address or AWS resource target and can choose where to send users using routing policies. CloudFront is a CDN: it caches and serves content from edge locations to reduce latency. In practice, Route 53 often points your domain to CloudFront, and CloudFront delivers the content.
- When should I use Route 53?
- Use Route 53 when you need a managed authoritative DNS service for your domain, especially if you want AWS-integrated routing to resources like ALBs, CloudFront, or S3 website endpoints. It’s also a good fit when you need DNS-based failover using health checks, multi-region routing (latency/geolocation), or controlled traffic shifting (weighted records) during migrations.
- How much does Route 53 cost?
- Pricing is usage-based. Common cost drivers include: (1) hosted zones (a monthly charge per hosted zone), (2) DNS queries (charged per million queries, varying by query type and region), and (3) optional health checks (charged per health check and sometimes per health-check query features). Your total depends mainly on how many domains/zones you host and your DNS query volume.
Category: networking
Difficulty: intermediate
Related Terms
See Also