Route 53 Alias record not pointing to S3 static hosted website

0
votes

I have bought a domain sandesh.link from route 53, created a publicly accessible S3 bucket with the same name, created a hosted zone and created an alias record pointing to the S3 static hosted website.

When accessing the domain, it shows that the domain is still parked at gandi.

I have updated the nameservers of the domain to the ones given in the hosted zone nameservers(can be seen at whois). I've also verified the domain through email.

How can I get this working?

1
amazon-web-servicesamazon-s3dnshostingamazon-route53
If you run DIG does it resolve your AWS Route 53 name servers? If so it could be that that the NS records have a longer TTL so you would need to wait for it to expire before everyone is resolving to Route 53. – Chris Williams
The domain shows Welcome folks Welcome. Is that correct? – Marcin
Oh, it does? It still shows the parked page on mine. But if it does, thats what I was trying to do. – Sandesh34
Yes, it works. Maybe you are loading website from local cache? – Marcin
Well, I tried clearing all cache, but its still same – Sandesh34

1 Answers

0
votes

Based on the comments.

The domain provided, when tested worked fine. It correctly showed:

Welcome folks Welcome

The reason it did not work before, could be that DNS changes were not fully propagated.