Ravindra BagaleCourses & study guides

Chapter 9: Domain Names, DNS and Subdomains

9.7 Alternative: GoDaddy registrar + Route 53 DNS

Companies running on AWS usually keep DNS in Amazon Route 53. It integrates with load balancers (Alias records), health checks and infrastructure as code. You can keep the domain registered at GoDaddy and only move DNS:

  1. AWS console → Route 53 → Hosted zones → Create hosted zone → Domain name example.com, Type Public hosted zone → Create.
  2. Route 53 creates NS and SOA records. Copy the four name servers (e.g. ns-123.awsdns-15.com, ns-456.awsdns-57.net, ...).
  3. Create record → Record name (empty) for the apex, type A, value 13.233.10.25, TTL 300 → Create records. Add another with record name www (type A to the EIP, or CNAME to example.com).
  4. At GoDaddy: My Products → your domain → DNS → Nameservers → Change nameservers → "I'll use my own nameservers" → enter the four Route 53 name servers → Save and confirm.
  5. Wait for the NS change (minutes to a few hours). Check with dig NS example.com +short. The Route 53 names should appear.

Records now live only in Route 53

After changing name servers, the records in GoDaddy's DNS page are ignored. Recreate any MX/TXT (email, verification) records in Route 53 before switching, or email will stop. A Route 53 hosted zone has a small monthly charge plus per-query charges. Delete unused hosted zones.

You can also register domains directly in Route 53 → Registered domains → Register domains. Route 53 then creates the hosted zone for you automatically.