Amazon Route 53 DNS Design - Routing Policies and Health Checks in Practice
Alias records and seven types of routing policies make advanced traffic control possible. This article introduces the design of multi-region failover using health checks.
Route 53 Basics and Alias Records
Route 53 is an authoritative DNS service provided by AWS that integrates three functions: domain registration, DNS routing, and health checks. One of the features of Route 53 is the alias record. In standard DNS, you cannot set a CNAME record at the Zone Apex (a naked domain such as example.com). Route 53 alias records work around this constraint and can map AWS resources such as CloudFront distributions, ALBs, and S3 static website endpoints directly to the Zone Apex. DNS queries to alias records are free, and no additional DNS resolution occurs as it does with CNAME, so they are advantageous in terms of both latency and cost.
Choosing Between Routing Policies
Route 53 has eight types of routing policies, and the main ones are listed below. Simple routing is basic routing to a single resource. Weighted routing distributes traffic across multiple resources by proportion, and you can use it in ways such as sending 10% of traffic to a new version in a canary release. Latency-based routing directs traffic toward whichever has lower latency to the user when you have resources in several AWS Regions. With an application deployed in Tokyo and Virginia, users in Japan are routed to the Tokyo Region and users in the United States are routed to the Virginia Region. Failover routing defines a primary and a secondary and switches automatically when a health check fails. Geoproximity routing can adjust the routing range with a bias value and is used to steer traffic to a specific Region.
Health Checks and Failover Design
Route 53 health checks periodically monitor the HTTP/HTTPS/TCP responses of endpoints from health checkers around the world. Health checks run at a fixed interval (such as 30 seconds), and when the number of consecutive failures of an endpoint reaches the threshold, it is judged unhealthy. Enabling fast health checks (10-second interval) shortens the interval and incurs an additional charge. In a multi-region failover design, you configure a health check on the ALB in the primary Region and specify the ALB in the secondary Region with failover routing. Health checks can integrate with CloudWatch alarms, and it is also possible to use the alarm state for the health check decision. This lets you use not only endpoint responses but also the application's custom metrics in failover decisions.
Route 53 Pricing
A Route 53 hosted zone costs $0.50 per zone per month (as of August 2026). DNS queries cost $0.40 per million queries for the first 1 billion queries/month, and queries to alias records are free. Using alias records for routing to CloudFront or ALB can reduce DNS query charges. Health checks cost $0.50 per check per month (AWS endpoints), and fast health checks (10-second interval) cost $1.00 per month. No additional charge is incurred for using latency-based routing or failover routing.
Hybrid DNS and Name Resolution
In environments where on-premises and cloud coexist, the design of bidirectional name resolution becomes important. With Route 53 Resolver, you can resolve private names inside a VPC from on-premises DNS, and conversely forward queries from inside a VPC to on-premises DNS. Using a private hosted zone that is valid only inside a VPC, you can manage internal names without exposing them externally. You enable cloud and on-premises servers to refer to each other by host name, creating a configuration that does not rely on specifying IPs directly. Designing name resolution correctly in a hybrid environment is the prerequisite for stable interconnection.
Putting Routing Policies to Advanced Use
Route 53 routing policies can be used in combination. With weighted routing, you can perform a canary release that shifts traffic to a new version little by little. You shorten wait times by distributing users to the nearest server according to their geographic location or steering them to a Region that responds quickly. Combined with health checks, you can automatically avoid endpoints that have failures. Combining multiple policies in stages results in a traffic design that matches requirements for availability / performance / staged releases.
Summary
With alias records and a wide variety of routing policies, Route 53 is a DNS service that handles cases ranging from simple DNS resolution to advanced traffic control. You combine health checks and failover routing to configure multi-region failover at the DNS layer. Because DNS is the foundation of infrastructure reliability, you also confirm the Route 53 SLA as a premise of the design.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
- Amazon Route 53 official page
- Amazon CloudFront official page
- Elastic Load Balancing official page
- AWS Documentation (official)
If this page and the official documentation disagree, treat the official documentation as authoritative.