Amazon Route 53 Explained

What is Amazon Route 53?

Amazon Route 53 is a highly available and scalable DNS web service from AWS. It is used to manage domain names, resolve DNS queries, perform health checks, and route traffic intelligently to application endpoints.

In simple terms, when a user types a domain name such as app.example.com into a browser, Route 53 helps answer the question: Where should this request go?

What does the name Route 53 mean?

The “53” comes from the TCP/UDP port number used by DNS. Route 53 is therefore named after the standard DNS service port.

Watch: AWS Route 53 Explained (Hands-on)

Prefer video learning? This tutorial explains Route 53 concepts, DNS flow, routing policies, and real-world use cases.

Why Route 53 matters in cloud networking

In cloud environments, many services sit behind load balancers, content delivery networks, or dynamic endpoints. Hardcoding IP addresses is not practical, scalable, or resilient. DNS becomes the abstraction layer that makes modern application delivery possible.

How Amazon Route 53 works

At a high level, Route 53 participates in DNS resolution. When a user requests your domain, Route 53 returns the correct DNS answer based on your hosted zone configuration and routing policy.

User enters https://app.example.com
                  |
                  v
          Browser asks DNS resolver
                  |
                  v
          Resolver queries Route 53 hosted zone
                  |
                  v
          Route 53 checks record + routing policy + health status
                  |
                  v
          Returns endpoint:
            - ALB DNS name
            - CloudFront distribution
            - Public IP
            - Another domain name
                  |
                  v
          User request goes to selected application endpoint

Step-by-step DNS flow

1. The user enters a domain name in the browser.
2. The browser or operating system sends a DNS lookup request to a resolver.
3. The resolver finds the authoritative DNS information for your domain.
4. Route 53 returns the configured DNS record response.
5. The browser connects to the returned endpoint and the application request starts.

Core Route 53 components

1. Hosted zones

A hosted zone is a container for DNS records for a specific domain.

• Public hosted zone: Used for internet-facing domains such as example.com.
• Private hosted zone: Used for internal DNS within one or more VPCs.

2. DNS records

These are the actual entries that map domain names to endpoints.

3. Alias records

Alias records are especially important in AWS. They let you map a domain directly to AWS-managed resources such as an Application Load Balancer or CloudFront distribution.

Unlike CNAME records, alias records can also be used at the zone apex, for example example.com.

4. Health checks

Route 53 health checks monitor the health of endpoints. They are commonly used with failover policies so that DNS answers change when the primary application becomes unhealthy.

Route 53 routing policies explained

One of the biggest strengths of Route 53 is that it can return different DNS answers depending on the routing policy you choose.

Weighted routing example

Imagine you are deploying a new version of an application. Instead of sending 100% of traffic to the new release, you can start with 10% and keep 90% on the old version. If things look stable, you can gradually increase the percentage.

Latency routing example

Suppose your application is deployed in Mumbai and Frankfurt. A user from India should ideally be routed to Mumbai, while a user from Europe should ideally be routed to Frankfurt. Latency-based routing helps Route 53 return the best endpoint.

Failover routing example

In a disaster recovery setup, the primary application may be running in one region and the standby application in another. If Route 53 health checks detect that the primary endpoint is unhealthy, DNS answers can automatically shift users to the backup environment.

Real-world Route 53 architecture example

Here is a common production-style traffic flow for an internet-facing application hosted on AWS:

In this architecture:

• Route 53 resolves the domain name.
• CloudFront improves global content delivery and edge caching.
• The ALB distributes traffic to healthy application targets.
• Your compute platform may be EKS, ECS, or EC2.

Terraform example for Route 53

Below is a simple example that creates a hosted zone and an alias record pointing to an Application Load Balancer.

resource "aws_route53_zone" "main" {
  name = "example.com"
}

resource "aws_route53_record" "app" {
  zone_id = aws_route53_zone.main.zone_id
  name    = "app.example.com"
  type    = "A"

  alias {
    name                   = aws_lb.app.dns_name
    zone_id                = aws_lb.app.zone_id
    evaluate_target_health = true
  }
}

What this Terraform does

• Creates a hosted zone for example.com.
• Creates a DNS record for app.example.com.
• Uses an alias record instead of a CNAME to point to an AWS load balancer.
• Enables target health evaluation for smarter DNS responses.

Common Route 53 mistakes

Using CNAME instead of Alias for AWS resources

This is one of the most common mistakes. Alias records are more appropriate for AWS-native resources and also support the root domain.

Forgetting TTL impact

DNS caching means changes do not always become effective immediately. A high TTL can slow down migrations and troubleshooting.

No health checks for failover design

If failover is required, health checks must be designed properly. Without them, DNS may keep returning a broken primary endpoint.

Private hosted zone confusion

Private hosted zones only resolve inside associated VPCs. They are not visible on the public internet.

Wrong record in the wrong hosted zone

A record created in the wrong hosted zone can lead to confusing behaviour, especially in organisations with multiple domains and subdomains.

Route 53 troubleshooting guide

Practical troubleshooting checklist

• Confirm whether the issue is DNS, load balancer, TLS, or application-related.
• Validate the hosted zone and record name carefully.
• Check whether the response is coming from public or private DNS.
• Review record TTL and recent changes.
• Confirm alias target values if pointing to ALB or CloudFront.
• Verify health check status if failover routing is involved.

Route 53 interview questions

Frequently asked questions

Related cloud networking resources