Complete Configuration Guide for AWS Route 53

Route 53 is Amazon Web Services’ (AWS) highly available and scalable Domain Name System (DNS) service. Beyond standard domain name resolution, it deeply integrates with other AWS services—such as EC2, S3, CloudFront, and Elastic Load Balancing (ELB)—to enable intelligent traffic routing, health checks, and failover capabilities.

📝 Phase 1: Preparation

Before you begin, please confirm the following:

• You have an AWS account
  → If not, sign up at aws.amazon.com.
  → A credit card is required (even for the Free Tier).

• You own a domain name
  → This can be a domain already registered elsewhere (e.g., GoDaddy, Namecheap), or a new one purchased directly through Route 53.

• You know your DNS resolution targets
  → Examples:

  • Point example.com to your EC2 instance’s public IP (54.200.10.5).
  • Point www.example.com to a CloudFront distribution.

⚙️ Phase 2: Host Your Domain in Route 53 (Create a Hosted Zone)

A Hosted Zone is a container for DNS records—similar to “DNS settings” in Alibaba Cloud.

Steps:

1. Log in to the AWS Management Console.
2. Search for Route 53 in the service bar and open it.
3. In the left menu, select Hosted zones.
4. Click Create hosted zone.
5. Fill in:
   • Domain name: example.com
   • Type: Usually select Public hosted zone
6. Click Create hosted zone.

✅ Upon success, Route 53 automatically generates NS (Name Server) and SOA (Start of Authority) records.

⚠️ The NS addresses (e.g., ns-123.awsdns-01.com) are the authoritative name servers you must configure at your domain registrar.

🔗 Phase 3: Delegate Your Domain to Route 53 (Update Name Servers)

This step determines who controls DNS resolution for your domain.

If your domain is registered elsewhere (e.g., GoDaddy):

1. Copy the 4 NS record values from your Route 53 hosted zone.
2. Log in to your domain registrar’s dashboard.
3. Locate Nameservers or DNS Servers settings.
4. Replace the default NS records with the 4 AWS NS records.
5. Save changes.

If you bought the domain in Route 53:

✅ No action needed! AWS automatically configures name server delegation.

🕒 Propagation time: Typically minutes to hours; full global sync may take 24–48 hours.

✏️ Phase 4: Add DNS Records (Resource Records)

Now you can freely configure A, CNAME, MX, and other record types in Route 53.

Example 1: Point root domain to an EC2 public IP

1. In your hosted zone, click Create record.
2. Configure:
   • Record name: Leave blank (represents @, i.e., example.com)
   • Record type: A – IPv4 address
   • Value: 54.200.10.5 (your server IP)
   • TTL: Default 300 seconds (adjustable)
3. Click Create records.

Example 2: Point www to CloudFront (use Alias)

Alias records are a Route 53-exclusive feature that lets you map domains (including root domains) to AWS resources—for free!

1. Click Create record.
2. Configure:
   • Record name: www
   • Record type: A – IPv4 address
   • Alias: Yes
   • Route traffic to: Select CloudFront distribution
   • Choose your CloudFront ID from the dropdown (e.g., d1a2b3c4d5e6f7.cloudfront.net)
3. Click Create records.

✅ Benefits of Alias records:

• Free (no additional query charges)
• Support root domains (example.com) pointing directly to CloudFront, ELB, or S3

🌐 Phase 5: Advanced Features (Intelligent Routing)

Route 53 offers multiple Routing Policies for high availability and smart traffic management.

1. Failover Routing

Automatically switch to a backup if the primary fails.

Steps:

• Create a Health Check:
  → Left menu → Health checks → Create health check
  → Protocol: HTTP/HTTPS/TCP
  → Target: Primary server IP or domain
  → Optional path: /health
  → Save

• Create Primary Record:
  → Record name: @
  → Routing policy: Failover
  → Failover record type: Primary
  → Associate with the health check
  → Value: 54.200.10.5

• Create Secondary Record:
  → Same name: @
  → Routing policy: Failover
  → Failover record type: Secondary
  → Value: 54.200.20.10 (backup IP)

✅ When the primary health check fails, Route 53 automatically returns the secondary IP.

2. Geolocation Routing

Route users based on their geographic location.

• US users → US server
• Users in Asia → Singapore server

Example:

• Record A:
  • Name: @
  • Policy: Geolocation
  • Location: United States
  • Value: 54.200.10.5
• Record B:
  • Name: @
  • Policy: Geolocation
  • Location: Asia
  • Value: 13.213.10.20
• (Optional) Default record for unmatched regions

3. Latency-Based Routing

Route users to the AWS region with the lowest network latency.

• Create one A record per region (e.g., us-east-1, ap-southeast-1)
• Set Routing policy to Latency
• Select the corresponding AWS Region
• Route 53 automatically returns the IP with the best latency for each user

🛡️ Phase 6: Security & Best Practices

❌ Avoid:

• Using standard A records for ELB/CloudFront (always use Alias)
• Skipping health checks (prevents automatic recovery)
• Setting TTL to 86400 (24 hours)—this severely delays failover

💰 Pricing Overview (2025 Reference)

💡 Most small websites cost under $1/month in total.

✅ Verify Your Configuration

Command-line testing:

dig example.com A
nslookup www.example.com

Online tools:

• https://dnschecker.org
• https://toolbox.googleapps.com/apps/dig/

In AWS Console:

• Check if Health Check status is Healthy
• Review CloudWatch Logs (if query logging is enabled)

🎯 Summary: Core Advantages of Route 53

✅ 100% SLA – Industry-leading availability guarantee
✅ Deep AWS Integration – One-click Alias to CloudFront, ELB, S3
✅ Intelligent Routing – Supports failover, geolocation, latency, weighted, and more
✅ Pay-as-you-go – No minimum fees; scales from personal projects to enterprise
✅ API-Driven – Fully automatable via AWS CLI or SDKs

Ideal for:

• Cloud-native applications (especially fully on AWS)
• Services requiring high availability and auto-failover
• Global architectures with multi-region deployments

If you’re already using AWS, Route 53 is almost always the best—and often the only—recommended DNS solution.