- Newest
- Most votes
- Most comments
Hello.
Have you purchased the domain "praveeny.com"?
If you have not purchased a domain, you will not be able to use it even if you create a public alias record in Route53.
If you want to purchase a domain with Route53, you need to follow the steps in the document below.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-register.html
I was able to confirm the following results using the "whois" command.
Do the NS records listed in "Name Server" in the results below match the NS records registered in the Route53 hosted zone?
If they do not match, please modify the NS records registered in the Route53 hosted zone so that they match.
whois praveeny.com
Domain Name: PRAVEENY.COM
Registry Domain ID: 2882341092_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com
Updated Date: 2024-05-19T22:26:06Z
Creation Date: 2024-05-17T20:36:26Z
Registry Expiry Date: 2025-05-17T20:36:26Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: abuse@amazonaws.com
Registrar Abuse Contact Phone: +1.2024422253
Domain Status: ok https://icann.org/epp#ok
Name Server: NS-1189.AWSDNS-20.ORG
Name Server: NS-1889.AWSDNS-44.CO.UK
Name Server: NS-26.AWSDNS-03.COM
Name Server: NS-719.AWSDNS-25.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-05-19T23:37:41Z <<<
I don't think it's very relevant, but the procedure in the document you used uses a slightly older procedure called OAI, so I recommend using the access control using OAC in the document below.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html
Relevant content
- asked 9 months ago
- asked 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Hi @riku. I have bought the domain through route 53. I deleted my hosted zone and recreated a new one. I also removed all the cdn step and now just hosting a simple s3 bucket with static website enabled. Still getting the same issue.
Now that you can check the NS record with the "dig" command, you can probably use it by registering CloudFront with an alias record. Also, even if you create a record, it may take some time for the domain to propagate, so please wait for a while before attempting to access it.
For static website hosting on S3, you need to create an S3 bucket with the same name as your domain name. https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html