4 ms·
There are bots that will check to see what zones are pointing to route53 and will then check to see if those zones are registered in route53. If not, they will
by LinuxBender 6y ago
There are bots that will check to see what zones are pointing to route53 and will then check to see if those zones are registered in route53. If not, they will register them and your domain is hijacked. Set up your domain in route53 before moving it, if you haven't. If AWS won't let you register the domain because someone beat you to it, point the root servers back to your old name servers and open a case with Amazon.
- wellthisisgreat 6y agoThank you, am I getting this right? Moving example.com from registrar to AWS 1. Register Hosting Zone in AWS (example.com) 2. Initiate the transfer for example.com, get to the part where they ask for Auth code 3. Initiate the transfer on registrar side, get the Auth code. 4. Enter the Auth code on AWS side. 5. Done? I am pretty sure that's what I did but after Step-4 that whole thing with goodprizwomen.com happened. Or did I miss something?
- LinuxBender 6y agoThat is the normal order of things. Probably the best you could do would be to open a case with Amazon and your current registrar and see if they can figure out where it went sideways.