- Newest
- Most votes
- Most comments
Say you own mycompany.com and its DNS is administered by a third party, and you want to start administering this in AWS Route 53. You start by creating a public hosted zone in Route 53 called mycompany.com and populating it with the records for that domain with your current registrar so that they match. Except for the NS records, leave the AWS-supplied records alone and when you're ready to cutover you need to update the NS records at your third-party registrar with the AWS nameservers. Your domain is now being administered through AWS Route 53 (although the registration is still with the third party).
This is described in greater detail in steps 1 to 9 of https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html
If you want to go the whole way and transfer the registration to AWS then it's step 10 of the above link, which redirects to https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-to-route-53.html
As far as I'm aware Route 53 isn't in scope of free tier (although plenty of other services are), well I can't find any mention of it in here https://aws.amazon.com/free/
The pricing structure is here https://aws.amazon.com/route53/pricing/ and you can generate an indicative quote using the calculator here https://calculator.aws/#/addService/Route53
Hi, thanks for your response! I am still quite confused on how to fill out this pricing form. i am unsure of what queries even are and for traffic flow, is that how much traffic we get to the site each day? Week? Month? year? This is all so new not sure this is the best way for me to go about setting up my DNS
Relevant content
- asked 7 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago