12. Domains and DNS: GoDaddy, Elastic IP, A/CNAME and Subdomains
12.4 Optional: Keeping DNS in Route 53
Companies AWS var astil tar DNS bahutek Route 53 madhe thevtat. Domain GoDaddy var thevun fakt DNS Route 53 la halavta yeto.
- AWS console → Route 53 → Hosted zones → Create hosted zone → Domain name
example.com, Type Public hosted zone → Create. - Route 53 creates NS and SOA records. Copy the four name servers (e.g.
ns-123.awsdns-15.com,ns-456.awsdns-57.net, ...). - Create record → Record name (empty) for the apex, type A, value
203.0.113.10, TTL 300 → Create records. Add another with record namewww(type A to the EIP, or CNAME toexample.com). - 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.
- 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.
Ravindra Bagale's Tip
Name servers Route 53 la halavlyavar students GoDaddy madhech records badlat rahtat aani "kahi hot nahi" mhantat. NS badlale ki GoDaddy che records ignore hotat. dig NS yourdomain.com +short ne aadhi bagha records nakki kuthe aahet.
Practice task
Draw a diagram showing the registrar, the DNS host and the EC2 server for two setups: GoDaddy DNS, and GoDaddy registrar with Route 53 DNS.