We bought our domain from Godaddy.com, then we changed the nameservers with the ones we got from Amazon 53. This name server shifting took around 30-40 hours.
In route 53, we used the Elastic IP of 1st EC2 instance A Name, Ipv4 address to host our mydomain.com website.
Then we had to shift our framework so we were testing on with another EC2 instance on mydomain.in website. After we successfully tested, we tried to route the new web server on mydomain.com by changing the IP address in Route 53 with the Public IP of 2nd EC2 instance, so that the mydomain.com points to the tested and ready 2nd Ec2 instance.
But the IP at route 53 for mydomain.com didn't happen immediately as in case of mydomain.in whose IP we replaced on the Godaddy site with the IP Address of 2nd instance. Due to the release of our product, we couldn't risk taking the mydomain.com offline by initiating the nameservers change on Godaddy.com to the original nameservers.
Currently we are redirectly all our mydomain.com hits to our mydomain.in website which we want to stop doing after a while.
Is there a way where we can route our mydomain.com to the 2nd EC2 instance without having a long downtime?
Is there a quickfix in the route 53 console?
Aucun commentaire:
Enregistrer un commentaire