What Is Amazon Route 53? AWS DNS Service Explained

Sunucun 4 min read

Short answer: Amazon Route 53 is AWS’s DNS service. It does three jobs: domain registration (buying domains), DNS management (pointing your domain to your server’s IP address or to an AWS resource) and health checking (keeping traffic away from a failed server). Its name comes from port 53, the port DNS uses.

Illustration: DNS

What Is Route 53 Used For?

When a visitor types your domain into a browser, DNS translates that name into an IP address. Route 53 acts as the authoritative DNS server that does this translation. What sets it apart from a classic DNS provider is its direct integration with AWS resources and its ability to spread traffic across targets based on latency, location or server health.

Key Concepts

  • Hosted zone: where the DNS records for a domain are stored. A public hosted zone answers queries from the internet; a private hosted zone resolves only from inside the VPCs you choose.
  • DNS records: A (IPv4), AAAA (IPv6), CNAME, MX (email), TXT (verification, SPF), NS and others.
  • Alias record: a Route 53-specific record type. It points a name to an AWS resource such as a CloudFront distribution, load balancer or S3 website. Unlike a CNAME, it can be added at the root of the domain (example.com), and alias queries to AWS resources are not charged.
  • Health check: regularly tests whether an endpoint responds; used with routing policies to stop traffic going to an unhealthy server.

Route 53 Routing Policies

According to the AWS documentation, Route 53 offers eight routing policies that determine how it answers queries for a record:

PolicyWhat it doesExample use
SimpleRoutes to a single resourceA site with one web server
FailoverActive–passive failover; switches to the backup if the primary is unhealthySwitch to a maintenance page if the main server goes down
GeolocationRoutes based on the user’s location (country, continent)Send visitors from Turkey to a Turkish server
GeoproximityRoutes based on the location of your resources; traffic can be shifted towards a regionBalancing load between regions
LatencyRoutes to the AWS Region with the lowest latencyAn application running in several Regions
IP-basedRoutes based on the IP block the query comes fromSend a specific ISP’s users to a specific endpoint
Multivalue answerReturns up to eight healthy records selected at randomSimple, health-checked load distribution
WeightedSplits traffic in proportions you setTesting a new version on 10% of traffic

How to Point a Domain to Route 53

  1. Open Route 53 in the AWS console and create a public hosted zone for your domain. Route 53 gives you four name servers (NS).
  2. Add your existing DNS records (A, MX, TXT, etc.) to the new hosted zone. Forgetting the email records is the most common problem after a move.
  3. In your domain registrar’s panel, replace the name servers with the four NS that Route 53 gave you.
  4. Wait for the change to propagate; how long depends on the TTL of the old NS records.
  5. Check it:
# See which name servers the domain uses
dig NS example.com +short

# Check the A record answer
dig A example.com +short

For DNS management in classic panels, see our CyberPanel DNS settings guide.

Route 53 Pricing

ItemPrice (AWS pricing page)
Hosted zoneUSD 0.50 per zone per month for the first 25 zones; USD 0.10 for additional zones. A zone deleted within 12 hours of creation is not charged.
Standard DNS queriesUSD 0.40 per million queries for the first 1 billion queries per month
Alias queries to AWS resourcesFree
Basic health check (AWS endpoint)USD 0.50 per check per month
Domain registrationAnnual fee that varies by extension

Prices can change; check the AWS Route 53 pricing page for current amounts.

Using Route 53 with Other AWS Services

  • EC2: an A record pointing to the server’s Elastic IP address. More: what is AWS EC2.
  • CloudFront and S3: an alias record pointing the domain to a CDN distribution or static site. More: what is CloudFront, what is S3.
  • VPC: a private hosted zone to give internal services names that resolve only inside the VPC. More: what is AWS VPC.
  • CloudWatch: alarms on health check results. More: what is CloudWatch.

Frequently Asked Questions

Do I need to buy my domain from AWS to use Route 53?

No. Your domain can stay registered elsewhere; you only need to point its name servers to Route 53.

Is Route 53 a load balancer?

No, it works at the DNS level. It can spread traffic with weighted, latency or multivalue policies, but connection-level load balancing needs a service such as Elastic Load Balancing.

Does Route 53 support DNSSEC?

Yes. DNSSEC signing can be enabled for public hosted zones, which protects against spoofed DNS responses.

Conclusion

Amazon Route 53 is a DNS service that combines domain registration, DNS management and health checking in one place and works directly with AWS resources. A simple A record is enough for a single-server site, while latency, failover and weighted policies keep multi-Region applications fast and available. If you’d rather run your own server outside AWS, take a look at our VDS server options.

Categories

Latest guides