Route 53 & DNS

AWS SAA SAA-C03 · Design Resilient Architectures

By Abu Anns · Last updated 20 November 2026Exam version: SAA-C03 (current)

Route 53: DNS in the cloud

Amazon Route 53 is AWS's Domain Name System (DNS) service. It translates human-readable domain names (like example.com) into IP addresses, registers domain names, and — most importantly for the exam — routes users to AWS resources using health-aware routing policies. Route 53 is a global service with 100% availability as its design target, and it is the exam's answer for almost any question involving domain names, DNS routing, or DNS-based failover.

A hosted zone is a container for DNS records for a domain. A public hosted zone holds records that are resolvable on the internet; a private hosted zone holds records that resolve only inside specified VPCs, which is how you give internal services friendly names like db.internal without exposing them publicly. Records map names to values: A records map a name to an IPv4 address, AAAA to IPv6, CNAME maps a name to another name, and NS and SOA records are created automatically for the zone. Route 53 also supports alias records, which are a Route 53 extension: an alias record maps a name directly to an AWS resource — an ELB, a CloudFront distribution, an S3 website endpoint, or another record in the same hosted zone — with no charge for the queries and automatic tracking of the target's changing IP addresses. Alias records can be used at the zone apex (the bare domain, example.com), where CNAME records are not allowed. When an exam question asks how to point a bare domain at a load balancer or CloudFront distribution, the answer is an alias record.

Routing policies: how Route 53 chooses an answer

PolicyBehaviorTypical use
SimpleReturns one value (or multiple in random order)A single resource; no health logic needed
WeightedSplits traffic by assigned weightsBlue/green deployments, A/B testing, gradual migration
Latency-basedRoutes to the Region with the lowest latency for the userMulti-Region applications where responsiveness matters
FailoverRoutes to a primary resource, switching to a secondary on health check failureActive-passive disaster recovery
GeolocationRoutes based on the user's geographic locationLocalized content, regulatory requirements, content licensing
GeoproximityRoutes based on geographic distance, with adjustable biasShifting traffic between Regions by distance
Multi-value answerReturns multiple healthy valuesSimple load balancing across healthy resources

The exam tests these policies by describing a requirement and asking which policy fits. The distinctions that matter most: weighted is for controlled traffic splits (a percentage to the new version); latency-based is for performance (nearest Region wins); geolocation is for location-based rules (users in Europe see the European site); failover is for disaster recovery (primary/standby). Note that latency-based routing measures latency between the user and AWS Regions, not geographic distance — a user can be geographically closer to one Region but have lower latency to another.

Health checks and failover

Route 53 health checks monitor the health of an endpoint — an IP address, a domain, or a CloudWatch alarm — by sending requests at intervals and checking the response. Health checks are what make failover and multi-value routing work: Route 53 only returns healthy endpoints. A failover configuration has a primary record and a secondary record; when the health check on the primary fails, Route 53 starts answering with the secondary. Health checks can also be based on CloudWatch alarms, which lets you fail over based on any metric — for example, failing over when the primary Region's error rate crosses a threshold, even if the endpoint still responds to pings. Health checks can be configured with a failure threshold (how many consecutive failures before marking unhealthy) and can monitor endpoints outside AWS too.

One subtlety worth knowing: DNS-based failover is not instant. Clients and resolvers cache DNS answers for the record's TTL, so some users may keep hitting the failed endpoint until their cached answer expires. A short TTL (such as 60 seconds) makes failover faster but increases query volume. This is why DNS failover is a good fit for disaster recovery measured in minutes, while Global Accelerator — which fails over at the network layer without DNS changes — is the better fit when failover must be nearly instant.

DNS in hybrid and private architectures

Route 53 also handles DNS for hybrid networks. Route 53 Resolver provides DNS resolution inside a VPC, including inbound endpoints (so on-premises systems can resolve names in your VPC) and outbound endpoints (so VPC resources can resolve on-premises names). Resolver rules let you forward queries for specific domains to your own DNS servers. For multi-account architectures, Route 53 Resolver endpoints can be shared across accounts, and private hosted zones can be associated with VPCs in other accounts. The exam rarely goes deep here, but the concept — Route 53 Resolver connects VPC DNS with on-premises DNS — is worth knowing.

Advanced Route 53: Resolver, Traffic Flow, and health checks

Beyond basic routing policies, Route 53 offers tools for complex and hybrid environments. Route 53 Resolver handles DNS resolution inside a VPC and bridges it with on-premises DNS: inbound endpoints let on-premises systems resolve names hosted in your VPC's private hosted zones, while outbound endpoints let VPC resources forward queries for specific domains to your own DNS servers. Resolver rules define which domains are forwarded where, and they can be shared across accounts in an organization so every VPC uses the same forwarding logic. Route 53 Resolver DNS Firewall adds a protective layer, blocking outbound DNS queries to known malicious domains and letting you define your own allow and block lists — useful for stopping malware that uses DNS to reach command-and-control servers.

Route 53 Traffic Flow is a visual editor for building complex routing configurations that combine multiple policies — for example, geolocation routing with failover inside each location, or weighted routing across latency-based endpoints. It also supports versioning, so you can roll a routing change back if it misbehaves. Health checks have depth worth knowing: a calculated health check combines the results of other health checks (for example, healthy if at least two of three endpoints respond), and a CloudWatch alarm health check lets Route 53 fail over based on any metric, such as an application error rate, rather than endpoint reachability alone. Health checks can monitor endpoints outside AWS, and you can configure the failure threshold (how many consecutive failures mark an endpoint unhealthy) and the request interval. Finally, Route 53 can register and manage domain names directly, and domain transfer lets you move an existing domain's registration to Route 53 without downtime.

One final practical detail: Route 53 charges a small monthly fee per hosted zone and per million DNS queries, and alias queries to AWS resources are free. Health checks are billed per check per month, so a design with many health checks across many endpoints should account for that cost — though it is usually small compared with the resources being monitored.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company wants its bare domain (example.com, with no subdomain) to point to an Application Load Balancer. The load balancer's IP addresses change over time. Which Route 53 record type should the solutions architect use?

Report an error

Q2.A company is deploying a new version of its website and wants to send 10% of user traffic to the new version and 90% to the current version, gradually increasing the share if the new version performs well. Which Route 53 routing policy should the solutions architect use?

Report an error

Q3.A company runs its application in two Regions: a primary Region and a standby Region. If the primary Region becomes unavailable, users must be routed to the standby Region automatically. Which Route 53 configuration meets this requirement?

Report an error

Q4.A global application is deployed in three Regions. The company wants each user to be routed to the Region that will give them the lowest network latency. Which Route 53 routing policy should be used?

Report an error

Q5.A company must show different website content to users based on the country they are connecting from, to comply with regional content licensing rules. Which Route 53 routing policy meets this requirement?

Report an error

Q6.A company has internal microservices running in a VPC. Developers want to reach the services by friendly DNS names (for example, orders.internal) that resolve only inside the VPC and are not visible on the public internet. Which solution meets this requirement?

Report an error

Q7.A solutions architect configures Route 53 failover between a primary and a secondary website. During a test, some users continue to reach the failed primary site for several minutes after failover. What is the MOST likely explanation?

Report an error

Q8.A company wants Route 53 to fail over to a secondary Region when the primary Region's application error rate exceeds a threshold, even if the primary endpoint still responds to health check pings. Which type of Route 53 health check supports this?

Report an error