I want to migrate the domain service from goDaddy to AWS. I'm an absolute beginner, please be aware of that and be considerate. Here's what I've done and what hasn't worked.
- I purchased a domain name example.com at goDaddy.
- I also have an EC2 instance running with the security settings all in place, an apache server running on it and an index.html file in the var/www/html folder. It seems to work fine when I open http://ec2-my-elastic-IP.eu-central-1.compute.amazonaws.com in my browser (don't know what the technical term is for this? is it a domain name?)
- Then I created a new hosting zone at Route 53, named example.com
- I created an A record pointing to my elastic IP for the EC2 instance. It has a TTL of 600 seconds and no Alias. The routing policy is simple and the name is simply empty, i.e. @.
- This didn't work. So I tried to make sense of the record data from the goDaddy site. Unfortunately it doesn't come in the BIND format, which could be imported into Route 53. Instead they supply a file which looks like this (replacing the numbers with xxxx):
; SOA Record example.com. 3600 IN SOA nsxx.domaincontrol.com. dns.jomax.net. ( xxxxxxxxxxx xxxxxx xxxx xxxxxxx xxxx ) ; A Records @ 600 IN A Parked ; CNAME Records www 3600 IN CNAME @ _domainconnect 3600 IN CNAME _domainconnect.gd.domaincontrol.com. ; MX Records ; TXT Records ; SRV Records ; AAAA Records ; CAA Records ; NS Records @ 3600 IN NS nsxx.domaincontrol.com. @ 3600 IN NS nsxx.domaincontrol.com.
- I tried converting this into the BIND format online without success. So I tried to create the records in the Route 53 environment that appear to be missing, namely two CNAME records. From the above file it looked like goDaddy has two CNAME records (I don't know what they do). Also within the Route 53 UI I didn't know which routing policy to select and whether I should select alias for those CNAME records, so I chose the simplest settings. After waiting for 24 hours, no website appears under example.com, just a blank page. I also created another A-record named www for the subdomain www.example.com (also pointing at the elastic IP from my EC2 instance). Nothing.
- Then I read this. It suggest that I should manipulate the DNS records at goDaddy, to update the four new name servers from AWS. But I can only edit the A and CNAME records and doesnt allow me to change the NS records.
- This question suggests to wait for 24 hours, but I did that a couple of times without success.
- This doesn't help, because I have no problems with my emails (yet), simply because I'm not bothered by that yet.