S3 Bucket + Route 53 + CloudFront

Question

Hello,  
  
I'm having some trouble resolving my website. I'm hosting my personal portfolio website statically on an S3 bucket, and was originally pointing my record sets to the S3 bucket itself.  
  
However, I set up a CloudFront distribution in order to provide SSL / TLS for my website. I can verify that the distribution resolves properly and I can visit my website via \[d14ngtcm7ru5in.cloudfront.net].  
  
I have also set a 4 record sets, 2 for \[ryanliu6.xyz] and 2 for \[www.ryanliu6.xyz] for both IPv4 and IPv6. However, the website fails to resolve and I'm honestly not sure why.  
  
Any help would be greatly appreciated,  
  
Ryan.

Accepted Answer

Hi,  
  
Probably not. DNS recursive resolvers cache the names of name servers for up to two days, so the DNS resolver that got the wrong name servers from Route 53 still is using those name servers. Folks who use a different DNS resolver should be able to access your website now if everything else is set up correctly. The _Route 53 Developer Guide_ explains how this works at a high level. See "How Amazon Route 53 Routes Traffic for Your Domain":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html#welcome-dns-service-how-route-53-routes-traffic  
  
Scott

Answer

Seems to be working here. Should probably work for you, too, by now.

Answer

Thank you and RobMM for replying. I have done as suggested but still am not able to access the website as expected.  
  
Was there something I've missed?  
  
Thanks

Answer

The nameservers assigned to your domain name don't have any DNS records for it. Check the NS records of your hosted zone in Route 53 for the correct list of nameservers you should be using. Then attach those to your domain via your registrar's control panel. If that's also Route 53, you can do so via "Registered Domains".

Answer

Hi,  
  
I took a look at your hosted zone and your domain. The name servers that Route 53 assigned to your hosted zone should also appear in two other locations:  
~ The NS record for the hosted zone  
~ The name servers that are associated with the domain registration  
  
The name servers in the NS record and the name servers for the domain are different from the name servers that Route 53 assigned to the hosted zone. Here's how you fix that:  
  
1. Get the name servers that Route 53 assigned to the hosted zone. See "Getting the Name Servers for a Public Hosted Zone" in the _Route 53 Developer Guide_:  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html  
  
2. Update the NS record in the hosted zone to use the name servers that you got in step 1. See "Editing Records":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-editing.html  
  
3. Update the domain registration to use the name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html  
  
Scott

S3 Bucket + Route 53 + CloudFront

Relevant content