DNS propagation after switch from Lightsail to EC2 / R53

0

Good Afternoon,

I had a small Lightsail instance that I was running a small web server on for the past year, with a domain that I had purchased. Everything was done through AWS. Domain registration in R53, and DNS in the Lightsail menu's.

This past week I had decided to upgrade this webserver and decided to switch to EC2 in order to facilitate future growth and just for the exposure to more of the AWS systems.

  • I built the server out and it works
  • All VPC / Routing is correct and I can access the site through it's Public (Elastic) IP.
  • The Domain was already registered in Route 53 and is still active
  • I deleted the Lightsail DNS Zone and created a Hosting Zone in R53 and created an A record for a subdomain of my domain and pointed it to the server.

This did not work, and after some troubleshooting I went back to Lightsail and recreated the old DNS Zone and it immediately worked and resolved to the old server. I had read that you need a base domain A record so I created that (not a subdomain, pointed at the same IP since it's the only resource available) and that has not worked either.

I understand that this sometimes takes time due to the old records TTL values, but using dig, nslookup, and whatsmydns I am not resolving to any older IP's, it's just not resolving at all and failing.

Currently in Route53 I have: NS record unchanged from default SOA record unchanged from default A record for my domain to my elastic IP A record for my subdomain to my elastic IP

Is there anything that I am missing? Is there some kind of DNS ownership transfer that I have to do between Lightsail and Route53 or is it all the same since it's AWS? Lightsail always feels slightly like a slightly different entity due to it's different UI but I'm not sure if that's the case or not.

Is there anything else I can do to check in the meantime outside of waiting for TTLs to expire? The TTLs from the Lightsail DNS are a mystery to me but I'm assuming it uses the same 2 day ones that R53 use. But even with that should it even matter the TTL on the A records are 300 and that's the only ones who's changed should have been significant (IP from Lightsail Static to Elastic IP tied to EC2).

Help me please! Thanks.

  • What is the error that you are seeing? Does it time out? Or gives you a specific error?

1 Answer
1

Hi,

Please make sure the NameServers in your registered domain in Route 53 Domains are same as the NameServers provided by the Route53 Hosted Zone. If not, update them to match those from the hosted zone to correctly delegate DNS management to that hosted zone.

Otherwise the registered domain and the Route53 Hosted Zone are not linked correctly and the domain name won't resolve because the DNS management NameServers the domain is delegating to are not the actual ones you, the domain owner, intend on using.

Thanks.

profile pictureAWS
EXPERT
AWS-SUM
answered 4 months ago
profile picture
EXPERT
reviewed 4 months ago
  • Thanks for the help. I checked the nameserver and they did not match so I went ahead and updated the Domain ones to match the Hosting Zone. When I did this it told me it could take up to 24hrs for propagation, of course. If it ends up fixing the issue I'll come back and accept the answer.

    Thanks again.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions