Route53 not updating website content through CloudFront

Question

I have updated my website content on S3. The website content looks good
http://pepo-site.s3-website.us-east-2.amazonaws.com/

I then updated the CloudFront configuration to point to the s3 bucket new url and the website, accessed from the Cloudfront URL, looks good too
https://d1839opyuqd21h.cloudfront.net/

However, my domain https://pepo.is/ still resolves to the old version of the website. How is this possible? The domain is configured to route traffic to the CloudFront distribution.

Here is the Route53 config:

![Route54](/media/postImages/original/IMqrLr5-2pQYyxa4dJYG-T8g)

I also invalidated the CloudFront distribution, but that should not be the cause, since https://d1839opyuqd21h.cloudfront.net/ already shows the correct content.

Answer

You domain isn't delegated to Route53. If I lookup the delegation set for pepo.is, I see 4 name servers dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net and dns4.p01.nsone.net.

% dig pepo.is -t NS

; <<>> DiG 9.10.6 <<>> pepo.is -t NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49036
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;pepo.is.			IN	NS

;; ANSWER SECTION:
pepo.is.		3600	IN	NS	dns1.p01.nsone.net.
pepo.is.		3600	IN	NS	dns2.p01.nsone.net.
pepo.is.		3600	IN	NS	dns3.p01.nsone.net.
pepo.is.		3600	IN	NS	dns4.p01.nsone.net.

These are not Route53 name servers. From the screenshot you shared the correct Route53 delegation set is:

ns-1105.awsdns-10.org.
ns-1594.awsdns-07.co.uk.
ns-209.awsdns-26.com.
ns-835.awsdns-40.net.

In order for you to fix this, you need to login to your account with your DNS registrar where you purchased pepo.is, and update the name server records on that website to the Route53 ones. Then you will need to wait up to 48 hours for the new name-servers to be available on the Internet, at which point your traffic will be routed to CloudFront and will be served as you expect.

Answer

Hello.

Have you configured the following documents?  
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html

Also, is the IP address below the IP address of the old site?  
``` bash
nslookup pepo.is
Server:         192.168.11.1
Address:        192.168.11.1#53

Non-authoritative answer:
Name:   pepo.is
Address: 46.137.195.11
Name:   pepo.is
Address: 13.215.144.61
```

A possible cause is that the settings are cached as described in the document below.  
This case may resolve itself over time.  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/troubleshooting-new-dns-settings-not-in-effect.html#troubleshooting-new-dns-settings-not-in-effect-cached-resource-record-set

Route53 not updating website content through CloudFront

Relevant content