Amazon Route 53

AWS’s authoritative DNS and domain registrar, with health checks and routing by latency, location or weight.

What it is: DNS
Type: Managed service on AWS
Made by: Amazon Web Services
License: Proprietary
Facts checked: 5 October 2026

What it is

Route 53 hosts your domain’s records in a hosted zone: public zones answer the internet, and private zones answer only inside the VPCs you attach them to. Each record has a routing policy that decides which answer a query gets. Simple returns one value. Weighted splits traffic by percentage, which is handy for canary releases. Latency sends users to the AWS Region that answers them fastest. Failover switches to a standby when a health check fails. Geolocation, geoproximity, IP-based and multivalue answer cover the rest.

Its AWS-specific feature is the alias record. A normal CNAME can’t sit at the bare domain (example.com), but an alias can, and it points straight at a CloudFront distribution, a load balancer, an API Gateway domain or an S3 website. Route 53 follows that resource’s IP addresses as they change, and queries to alias records for AWS resources are free. A hosted zone costs $0.50 a month for the first 25, and standard queries $0.40 per million.

Why teams pick it

Alias records work at the zone apex and cost nothing to query when they point at AWS resources
Health checks plus failover, latency and weighted routing give you DNS-level traffic steering
Private hosted zones give VPCs internal names without running your own DNS servers
Registrar, DNS and certificate validation all in one AWS account

Watch out for

DNS failover is only as fast as resolvers honour TTLs; clients may keep a stale answer for a while
Latency and geolocation queries cost more than standard ones ($0.60 and $0.70 per million)
Alias records only point at a set list of AWS resources; anything else needs a CNAME
Health checks are billed per check per month: $0.50 for AWS endpoints (the first 50 in your account are free) and $0.75 for others

How it fits with other technologies

What Amazon Route 53 uses

Change batch: point the bare domain at CloudFront with an alias · json

{
  "Changes": [{
    "Action": "UPSERT",
    "ResourceRecordSet": {
      "Name": "acme.example.",
      "Type": "A",
      "AliasTarget": {
        "HostedZoneId": "Z2FDTNDATAQYW2",
        "DNSName": "d111111abcdef8.cloudfront.net.",
        "EvaluateTargetHealth": false
      }
    }
  }]
}

See it in a real stack

No architecture uses Amazon Route 53 yet. Drop it into the playground and wire it up yourself.Open playground →

Where it came from2010–2026

By 2010 you could run almost a whole application on AWS, but not its name. DNS still lived with a registrar, a specialist DNS company or your own BIND servers, configured separately from the EC2 instances and load balancers it pointed at, whose addresses changed as you scaled. Getting DNS wrong takes a site offline as surely as losing its servers.

AWS announced Amazon Route 53 on 5 December 2010 and made it generally available in May 2011, adding weighted routing and integration with Elastic Load Balancing. The “53” is the TCP and UDP port DNS servers listen on. Its name servers sit on a global anycast network, so each query is answered by a nearby location. In 2012 latency-based routing brought “the same latency based routing technology that powers Amazon CloudFront” to customers’ own records.

Route 53 then took on more of the job: health checks and DNS failover in 2013, domain registration and private zones for VPCs in 2014, and resolvers for hybrid networks in 2018.

Why it’s built this way

Anycast name servers around the world: Many locations announce the same addresses, so resolvers reach the closest one and traffic shifts to another site automatically if one fails.
Shuffle sharding of name servers: DNS hosts are frequent DDoS targets. Route 53 gives each domain its own set of four out of 2,048 virtual name servers, so an attack on one domain is unlikely to take out every server another domain depends on.
Alias records for AWS resources: Load balancer IP addresses change, and a CNAME isn’t allowed at a bare domain. An alias looks up the resource’s current addresses itself, so example.com can point straight at a load balancer or CloudFront.
Routing decisions inside DNS: Customers wanted apps that span several Regions. Weighted, latency and failover policies let the DNS answer itself steer users, with no extra proxy in the path.

Timeline

2010
Amazon Route 53 announced on 5 December
2011
Generally available in May with weighted routing and load balancer aliases
2012
Latency-based routing across AWS Regions
2013
Health checks and DNS failover
2014
Domain registration, geolocation routing and private hosted zones for VPCs
2018
Route 53 Resolver links VPC and on-premises DNS
2026
Global Resolver, an internet-reachable anycast DNS resolver for an organization’s own clients, becomes generally available

Sources9 · facts checked 5 October 2026

Improve this page on GitHub