- Newest
- Most votes
- Most comments
This issue could be caused by several factors. Let me walk through some troubleshooting steps:
-
DNS Propagation: If you recently created or updated your CloudFront distributions, it may take up to 24-48 hours for DNS changes to fully propagate, though it's typically much faster.
-
Distribution Status: Even though the console shows "Deployed," there might be an underlying issue. Sometimes there can be a discrepancy between the displayed status and the actual deployment across all edge locations.
-
DNS Resolution Tools: Try using different DNS lookup tools like 'dig' or 'nslookup' with alternative DNS servers (e.g., Google's 8.8.8.8) to see if the issue is with your local DNS resolver:
dig @8.8.8.8 d2yll4dztupvtv.cloudfront.net
nslookup d2yll4dztupvtv.cloudfront.net 8.8.8.8
-
Recent Changes: If you recently deleted and recreated these distributions, or made significant changes, there might be DNS caching issues. In such cases, you may need to wait for DNS caches to clear (typically 15 minutes to a few hours).
-
Edge Location Issues: There could be problems with specific CloudFront edge locations that are affecting your distributions.
-
Service Disruption: Although rare, there could be a partial service disruption in CloudFront affecting your distributions.
If the issue persists after trying these troubleshooting steps, I recommend contacting AWS Support as they can access more detailed information about your distributions' performance and any potential service-wide issues that might be affecting the DNS resolution.
Sources
all of my cloudfront domain request fail | AWS re:Post
I remove my cloudfront deployment and create it again. But, When i create new deployment and use my prev domain, it can't access and error is occured. | AWS re:Post
The CloudFront Distribution did not handle requests from outside for two hours 18.01.25. | AWS re:Post
answered 10 months ago
