Build Route 53 DNS record configurations for A, AAAA, CNAME, MX, TXT, and alias records.
Last verified: April 2026
Maps a hostname to an IPv4 address, e.g. 192.0.2.1
Output will appear here...The Route 53 Record Builder helps you construct DNS record configurations for Amazon Route 53 hosted zones. It supports all common record types including A, AAAA, CNAME, MX, TXT, SRV, and alias records with routing policies like weighted, latency-based, failover, and geolocation. The tool generates ready-to-use configurations for the AWS CLI, CloudFormation, and Terraform, reducing syntax errors in DNS management.
An alias record is a Route 53-specific extension that maps a domain name to an AWS resource (ALB, CloudFront, S3) at the DNS protocol level, returning the resource's IP addresses directly. Unlike CNAMEs, alias records work at the zone apex (e.g., example.com) and incur no Route 53 query charges when pointing to AWS resources.
No. This tool runs entirely in your browser and generates configuration snippets you can copy into the AWS CLI, CloudFormation templates, or Terraform files. It never accesses your AWS account.
Route 53 supports simple, weighted, latency-based, failover, geolocation, geoproximity, multivalue answer, and IP-based routing policies. Each policy controls how Route 53 responds to DNS queries, enabling traffic distribution, disaster recovery, and regional routing strategies.
You're setting up a blue-green deployment for your production API. You need weighted routing records that send 90% of traffic to the current (blue) ALB and 10% to the new (green) ALB, with health checks on both. Using the builder, you generate two weighted alias records with the correct HostedZoneId for each ALB, proper SetIdentifiers, and associated health checks. Over the next hour, you gradually shift the weight from 90/10 to 0/100. When a bug appears in the green deployment, you flip the weight back to 100/0 in under a minute.
The builder constructs Route 53 resource record set configurations by combining the record name, type, and routing policy into the correct JSON structure for the AWS API. For alias records, it generates the HostedZoneId and DNSName of the target resource. For routing policies, it adds the appropriate policy-specific fields (Weight for weighted, Region for latency, SetIdentifier for all non-simple policies). Output is generated in AWS CLI JSON, CloudFormation YAML, and Terraform HCL formats.
Use alias records instead of CNAMEs whenever pointing to AWS resources. Alias records work at the zone apex (naked domain), are free for queries to AWS resources, and resolve faster because Route 53 returns the IP directly instead of requiring a second DNS lookup. The only reason to use a CNAME is for non-AWS targets.
Always associate health checks with failover records. Without a health check, Route 53 will continue routing traffic to a downed primary endpoint until you manually update the record. Health check pricing ($0.50-$1.00/month) is negligible compared to the cost of sending users to a dead endpoint for hours.
TXT record values must be enclosed in double quotes within the record data, and individual strings are limited to 255 characters. For SPF or DKIM records that exceed 255 characters, you must split them into multiple quoted strings within the same TXT record. This trips up nearly everyone configuring email authentication.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.