Godaddy is one of the oldest and widely used domain services provider but after after having Route53 from AWS (Amazon Web Services) it is almost necessary (as per a developer and automation perspective) to move to Route53 or any other DNS provider which provides us APIs and other services to automate around the domains. Due to this requirements, I had to move a few domains to Route53 from GoDaddy.
Migrating domains from one DNS provider to another is a big decision and requires careful planning to avoid any down time. When we were doing this we planned this adequately and followed these steps which I believe can be helpful for others as well.
- Reduce TTL for every record to a few minutes so when we are moving they start sending traffic to Route53 immediately. This is not a required step but recommended if you want to test it quickly. If your current TTL time is in days or weeks then this will take that much time to go live.
- Export zone file from GoDaddy.
- Import zone file into Route53.
- Announce downtime for maintenance on scheduled date to your customers.
- Initiate transfer from Route53. Refer to #2 in references.
- Accept and authorize it from GoDaddy. Refer to #3 in references.
- Verify the changes.
- After completing migration, we will need to run the following for each record from zone file to make sure it is responding to DNS query both with name server and without it:
- dig +noauthority +noquestion +nostats myDomain.com
- dig +noauthority +noquestion +nostats myDomain.com @ns-AWS-DNS.
- nslookup -debug myDomain.com
- nslookup -debug myDomain.com ns-AWS-DNS.
- traceroute myDomain.com