AWS Route53 DNS Setup Guide

How to Configure DNS Records on AWS Route 53

AWS Route 53 is Amazon's highly scalable cloud DNS service, offering 100% uptime SLA and global anycast routing. This guide explains how to manage DNS records in Route 53, from basic A records to advanced routing policies for load balancing and failover.

Step-by-Step Setup Guide

1. Access AWS Route 53 Console Log into AWS Management Console and navigate to Route 53.
   • Search for 'Route 53' in the AWS services search bar
   • Click on 'Hosted zones' from the left navigation menu
   • Select your domain's hosted zone from the list
   • If you don't see your domain, create a hosted zone first
2. Navigate to Hosted Zone Click on your domain name to view existing DNS records.
   • You'll see NS (nameserver) and SOA records created automatically
   • These records are required for DNS to function - don't delete them
   • Note your Route 53 nameservers if you need to update your registrar
3. Create DNS Record Click 'Create record' button to add a new DNS entry.
   • Choose 'Simple routing' for standard DNS records (most common)
   • Enter record name (leave blank for root domain, or add subdomain)
   • Select record type (A, AAAA, CNAME, MX, TXT, etc.)
   • Enter value(s) - IP address, hostname, or text content
   • Set TTL (300 seconds default, or custom value)
   • Click 'Create records' to save
4. Update Nameservers at Registrar Point your domain registrar to Route 53 nameservers.
   • Copy the 4 NS record values from your hosted zone
   • Log into your domain registrar (where you purchased the domain)
   • Update nameservers to the 4 Route 53 NS values
   • Nameserver changes take 24-48 hours to propagate globally
   • Once propagated, Route 53 becomes authoritative for your domain

Common DNS Record Types on AWS Route 53

• A Record: Maps domain to IPv4 address. Leave name blank for root domain or enter subdomain. Can use alias records to point to AWS resources (ELB, S3, CloudFront) with zero TTL and no charges. Name: (blank), Type: A, Value: 192.0.2.1, TTL: 300, Routing: Simple
• CNAME Record: Creates alias to another domain. Cannot be used on root domain - use Alias record or A record instead. Common for subdomains and third-party service integrations. Name: www, Type: CNAME, Value: example.com, TTL: 300, Routing: Simple
• MX Record: Routes email to mail servers. Value includes priority (lower = higher priority) followed by mail server hostname. Add multiple MX records for redundancy. Don't forget trailing dot for FQDN. Name: (blank), Type: MX, Value: 10 mail.example.com, TTL: 300, Routing: Simple
• TXT Record: Stores text for verification, SPF, DKIM, DMARC, and domain ownership. Enclose values in quotes if they contain spaces. Multiple TXT values can exist for one name. Critical for email authentication. Name: (blank), Type: TXT, Value: "v=spf1 include:_spf.google.com ~all", TTL: 300

Troubleshooting Common Issues

• DNS records not resolving after creation: Verify your domain registrar is pointing to the correct Route 53 nameservers (check NS records in hosted zone). Nameserver changes take 24-48 hours. If nameservers are correct, verify record syntax - FQDN should end with a dot, or leave blank for Route 53 to append your zone. Use our DNS checker to verify global propagation.
• Cannot create CNAME on root domain: AWS Route 53 supports Alias records as a solution. Instead of CNAME, create an A record with 'Alias' enabled, pointing to your AWS resource (ELB, CloudFront, S3). Alias records work at root domain and are free (no query charges).
• High Route 53 costs from DNS queries: Route 53 charges $0.40 per million queries (first 1 billion/month). Reduce costs by: increasing TTL values to cache records longer, using Alias records for AWS resources (no query charges), consolidating multiple A records into one with multiple IP values, implementing CloudFront caching.
• Email delivery failures with MX records: Ensure MX record values include priority number (e.g., '10 mail.example.com'). Verify mail server hostnames have corresponding A records. Check SPF, DKIM, DMARC TXT records are configured. MX records must point to A records, not CNAME records. Use our DNS lookup to verify MX propagation.

Frequently Asked Questions

• What's the difference between A records and Alias records in Route 53? A records map to IP addresses and are charged per query. Alias records are AWS-specific, pointing to AWS resources (ELB, S3, CloudFront, API Gateway) with no query charges and automatic IP updates. Alias records can be used on root domains, while CNAME cannot. Use Alias records for AWS resources, A records for external IPs.
• How much does AWS Route 53 cost? Hosted zones cost $0.50 per month per zone. DNS queries are $0.40 per million queries (first 1 billion/month). Alias queries to AWS resources are free. Health checks are $0.50/month per endpoint. Most small websites pay $0.50-$2/month. Route 53 is more expensive than free DNS providers but offers 100% uptime SLA and advanced routing.
• How long does Route 53 DNS propagation take? Route 53 propagates changes to all AWS edge locations within 60 seconds. Global propagation to ISPs and resolvers depends on TTL values and varies from minutes to 48 hours. Lower TTL (60-300 seconds) enables faster changes but increases query costs. Use our global DNS checker to monitor propagation across worldwide servers.
• Should I use Route 53 if I'm not using other AWS services? Route 53 offers excellent reliability (100% uptime SLA) and advanced features (geolocation routing, health checks, failover) but costs more than free DNS providers. Use Route 53 if you need enterprise-grade DNS, traffic routing policies, or AWS integration. For simple DNS needs, free providers like Cloudflare offer good performance at no cost.