Help improve AWS Support Official channel in re:Post and share your experience - complete a quick three-question survey to earn a re:Post badge!
Why is mt CNAME not Working
My CNAME (unigram95.net from Route 53) is not working even though my distribution domain name (https://d1jp9i4abboo32.cloudfront.net) is working, and I have configured the distribution to use an alternate domain name.
- Newest
- Most votes
- Most comments
I can’t find a dns record for the domain to point to cloudfront. Therefore You will need to create an alias record for the domain in route53 to point to your Cloudfront distro.
Please follow the steps here
Configuring Amazon Route 53 to route traffic to a CloudFront distribution https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-cloudfront-distribution.html
It’s pretty quick tbh. Please confirm your domain glue records match the correct DNS name servers of your hosted zone in route53. Then double check you have created the alias correctly.
Did you create a cname or an alias? If I recall correctly Cnames are not supported on the root of a domain in r53
I have create two records as specified in the wiki because IPv6 is turned on for the distribution, but, I'm still unable to hit the site using my CNAME. Does it take some time before it propagates? How long? To reply to your third comment, I created two aliases under the CNAME.
CNAME can't be attached to zone apex directly, try to create A Record (Alias record) which points out to zone apex.
Hey, Please make sure your domain is registered at Route 53. Coz i can't find any NS record of this domain.
Can you also share the screenshot of Route53 entry?
It should be something like this
There are 5 records on the domain, please see the screen shot.
Theres your problem. Your Records are invalid. It doesnt look like you setup the Alais correctly. It looks like you pasted the record and didnt select the cloudfront distro from the drop down in the GUI Follow the instructions in the link provided in my answer. Ensure you use the GUI and select the cloudfront and do NOT paste the cloudfront URL in.
Relevant content
- asked 2 years ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago
It would be appreciate if you accept the correct answer which points to the dns records missing, for the time spent helping