- Newest
- Most votes
- Most comments
Based on your description, there are several potential reasons why your static website at casayank.com can't be reached despite the S3 endpoint working correctly.
Since you mentioned that the S3 website endpoint (http://casayank.com.s3-website-us-east-1.amazonaws.com/) works fine, the issue is likely related to your DNS configuration rather than the S3 bucket setup itself.
Here are some things to check:
-
DNS Propagation: If you recently transferred the domain from GoDaddy to Route 53, DNS changes can take 24-48 hours to fully propagate across the internet. This could explain why your site isn't accessible yet.
-
Route 53 Configuration: Verify that your Route 53 hosted zone has the correct A record or Alias record pointing to your S3 bucket. For an S3 static website, you should have an A record (Alias) pointing to the S3 website endpoint, not the regular S3 bucket endpoint.
-
Nameserver Configuration: Ensure that your domain is using the Route 53 nameservers. When you register a domain with Route 53, it automatically creates a hosted zone with the correct nameservers, but you need to make sure these are being used.
-
Domain Registration Status: Since you mentioned deleting and re-registering the domain, check that the domain registration is fully active and not in any pending state.
-
Browser Cache: Try accessing the site from a different browser or after clearing your cache to ensure it's not a local caching issue.
-
CloudFront: If you're using CloudFront with your S3 bucket, make sure your distribution is properly configured with the correct origin (S3 website endpoint) and that your domain name is added as an alternate domain name in the CloudFront distribution.
Since casayank.org works fine with the same setup, it's likely a specific issue with the casayank.com domain configuration. The fact that you deleted and re-registered the domain could indeed be contributing to the problem, especially if there are lingering DNS records or propagation delays.
Sources
My site doesn't shows up when using the domain name | AWS re:Post
DNS-PROBE_POSSIBLE - S3 Static Website | AWS re:Post
Use Amazon S3 website hosting to host without a single web server - Hosting Static Websites on AWS
Unable to host a static website with S3 at a DNS name registered in Route 53 due to bucket name squattered by spammer | AWS re:Post
Hello.
I performed a DNS propagation check on the following website, but "casayank.com" could not be resolved.
I also checked the NS records, but I was unable to resolve the names in some countries.
So there may be a problem with your DNS settings or hosted zone.
It may be that it takes time for the domain to propagate.
https://whatsmydns.me/#A/casayank.com
https://whatsmydns.me/#NS/casayank.com
The fact that http://casayank.com.s3-website-us-east-1.amazonaws.com/ works, but casayank.com doesn't, strongly indicates a DNS configuration issue in Route 53, specifically with the A record for casayank.com.
Even though the AWS Test Record tool shows a green checkmark, that tool only verifies that the record exists and can be queried by Route 53. It doesn't guarantee that external DNS resolvers are correctly pointing to Route 53 or that the A record is configured to point to the correct S3 static website endpoint.
Get Route 53 Name Servers:
- Go to the Route 53 console.
- Click on "Hosted zones" and select the hosted zone for casayank.com.
- In the details pane, you will see the "Name servers" listed (usually four). Copy these.
Check GoDaddy Name Servers:
- Log in to your GoDaddy account (or wherever you manage the casayank.com domain registration).
- Navigate to the DNS management settings for casayank.com.
- Verify that the Name Servers listed there are the exact same four Name Servers you copied from Route 53.
Update if Necessary:
- If the GoDaddy Name Servers are not the Route 53 Name Servers, update them in GoDaddy.
- This change can take up to 48 hours to propagate globally (DNS propagation), though it often happens much faster (within minutes to a few hours).
Thank you for your reply. As I mentioned, it was originally (mistakenly) purchased it via GoDaddy. I deleted it in GoDaddy and after a few days was able to purchase it via AWS Route 53. There is been more than a week since I registered domain in Route 53, so I can hardly blame it on a timing delay. Yet, considering that the other domain works, I am out of ideas what I can do.
Thank you, I did try the tool and got the same results. Here is how the casayank.com is set up. Seemingly, the same way as casayank.org, which is working. Do you see anything wrong with it? Unfortunately, I am database guy :(. TIA! casayank.com A Simple
Yes s3-website-us-east-1.amazonaws.com.
No
casayank.com NS Simple
No ns-1151.awsdns-15.org. ns-460.awsdns-57.com. ns-1800.awsdns-33.co.uk. ns-742.awsdns-28.net. 172800
casayank.com SOA Simple
No ns-1151.awsdns-15.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 900
www.casayank.com A Simple
Yes s3-website-us-east-1.amazonaws.com.
No