AWS cloud
Route 53 routing policies
Route 53 routing policies decide which answer a DNS query gets: split traffic by weight, send users to the lowest-latency region, fail over to a standby, route by the user's country or network. Combined with health checks, they're the backbone of multi-region and disaster-recovery designs on AWS. Senior interviews expect you to know all eight policies, how health checks drive them, how to nest policies for real architectures, and — crucially — the limits of DNS-based traffic management.
After this topic you can
- Choose a routing policy (weighted, latency, failover, geolocation)
- Combine policies with health checks for failover
- Plan blue/green and regional traffic shifts with DNS
Lessons
-
1How routing policies work
- Record sets with set identifiers
- The eight policies
- Health checks + evaluate target health
- TTL is always in play
-
2Simple and multivalue answer
- Simple
- Multivalue answer
-
3Weighted routing
- How weights work
- Uses
- Why weighted DNS is imprecise for canaries
-
4Latency-based routing
- How it decides
- Caveats
-
5Failover routing
- Active-passive
- Failover timing
- "Failover isn't switching even though the primary is down"
-
6Geolocation, geoproximity and IP-based routing
- Geolocation
- Geoproximity (Traffic Flow)
- IP-based routing
- Latency vs geolocation in one line
-
7Health checks in depth
- Types
- Settings
- Design a meaningful health endpoint
- Flapping
- Cost
-
8Combining policies and real designs
- Nesting with aliases
- Design: global app with EU data residency
- Design: active-passive DR with a maintenance page
- Design: migrate traffic to a new account/stack
- Design: route a customer by office IPs
- Testing before go-live
-
9Limits of DNS-based traffic management
- What DNS can't do
- Complementary AWS services
-
10Interview questions and model answers
- "Name the Route 53 routing policies and when you'd use each."
- "Latency vs geolocation routing?"
- "Why not use weighted DNS for a 5% canary?"
- "Failover isn't happening although the primary is down. What do you check?"
- "How would you health-check a private endpoint?"
- "Design global routing: EU users must stay in the EU, everyone else should get the fastest region, with failover."
- "Can you fail over a database with Route 53?"
- "Which routing policy have you used and why?" (how to answer)