Hi All, this document tells you how to migrate DNS from GoDaddy to AWS route 53.
DNS plays an important role whenever the application is hosted. Consider your DNS system is down where all you public applications are hosted. This will impact your business which results in huge money loss. During this condition, you choose a provider where they can ensure 99.99999% of uptime. In this condition, you may migrate from your existing DNS management service provider to one which ensures higher uptime.


In this document, I will tell how to DNS migrate from GoDaddy to AWS Route 53. This doesn’t mean that GoDaddy provides higher uptime, it does!!
Still, there are some people who have confusion that both DNS and Domain should be hosted with the same provider. Its nothing like that DNS for all your application works with NAME Server.
Whenever there is a request to your application, Once it reaches the domain nameserver it tells where your DNS in located and picks the exact record which is required.

Prerequisites

1. You should have AWS console access with AWS Rout53 privileges
2. Godaddy account with required privileges.

Migration Process

Step 1: Goto AWS Route 53 Console
Step 2: Create Create Hosted Zone
Step 3: Enter your Domain name with any mistakes.
Step 4: Now you can see inside your created hosted zones has Nameserver entry has created.
Step 5: Now Goto Godaddy account and export the all the records, For exporting Goto DNS and Export Zone file.
Step 6: Now to Goto newly Created Hosted Zone and Select import Zone file, if you get an error try to add the entries manually.
Step 7: Copy the 4 Nameservers from newly Created Hosted Zone in AWS Route 53 and replace the Nameserver section in Godaddy.
Step 8: This process will take some time depends on time to live configuration of your provider.
Step 9: You can check whether your name server is migrated to AWS Route 53 or not using mxtoolbox.com or using dig command in the command line

dig example.com

dig NS techrunnr.com

; <<>> DiG 9.11.2-P1-1-Debian <<>> NS techrunnr.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54159
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;techrunnr.com. IN NS

;; ANSWER SECTION:
techrunnr.com. 3587 IN NS ns-2041.awsdns-63.co.uk.
techrunnr.com. 3587 IN NS ns-3041.awsdns-63.co.uk

;; Query time: 236 msec
;; SERVER: 92.222.97.145#53(92.222.97.145)
;; WHEN: Wed Dec 19 10:23:13 IST 2018
;; MSG SIZE rcvd: 94

This is the sample output of the dig command.

Now you can see domain name server has migrated to AWS Route 53. Now, whenever you need to add or change Name server you have to do modification in AWS Route 53, not in Godaddy. Ideally, No more Godaddy manages you DNS.

© 2018, Techrunnr. All rights reserved.

#1
#2
#3
Questions Answered
Articles Written
Overall Points
Categories: AWS

Prabhin Prabharkaran

He is Technical professional. He is a person who loves to share tricks and tips on the Internet. He Posts what he does!!

Leave a Reply

Please wait...

Subscribe to our newsletter

Want to be notified when our article is published? Enter your email address and name below to be the first to know.