Opscraft
Route 53 routing policies · Lesson 2 of 10 · 3 min read

Simple and multivalue answer

Simple

app.example.com  A  300  203.0.113.10  203.0.113.11  203.0.113.12
  • One record set; may contain multiple values, returned all together in random order (clients usually try the first).
  • No health checks — a dead IP keeps being returned.
  • Fine for a single ALB alias, a single CloudFront distribution, a fixed IP.

Multivalue answer

set-id web-1  A  60  203.0.113.10  health-check: hc-web-1
set-id web-2  A  60  203.0.113.11  health-check: hc-web-2
set-id web-3  A  60  203.0.113.12  health-check: hc-web-3
  • Each value is its own record set with its own health check.
  • Route 53 returns up to 8 healthy values, randomly selected per query.
  • Gives clients several healthy targets to try — client-side load spreading with health filtering.
  • It's not a load balancer: no connection draining, no even distribution, no TLS termination, no awareness of load; DNS caching still applies. For real load balancing use an ELB; multivalue is useful for things like a fleet of DNS/UDP servers or as a simple, cheap redundancy layer.
Enlarge diagramclient203.0.113.10healthy: returned203.0.113.11health check failing: left out203.0.113.12healthy: returnedRoute 53up to 8 healthy
Figure 1. Multivalue answers give clients several healthy IPs to try. Useful, but not a load balancer.
Swipe sideways to see all of it, or tap to open it full screen.