why are my non www https url not working?

Question

I created a static s3 bucket site that works. I created a certificate for:

with additional names:

In my DNS I successfully attached all 2 certificates. Yes, all 2 because the wildcard and the blank subdomain were the same CNAME values.

In the DNS I have www.example.com CNAME going to the cloudfront url.

I figured maybe this was the issue and I should use no www and also try a wildcard, but both simply didn't work and nothing loaded.

I then created a CloudFront and attached the certificate to it with Alternate Domain Names (CNAMEs)

In CloudFront my Viewer Protocol Policy is REDIRECT TO HTTPS

The behavior:

https://www.example.com works
http://www.example.com works (redirects to https://www.example.com)
www.example.com works (redirects to https://www.example.com)
example.com works (redirects to https://www.example.com)
https://example.com breaks with a (fail) and then auto attempts with (failed)net::ERR_NAME_NOT_RESOLVED
http://example.com breaks with a (fail)

One other thing is, I do have a separate certificate for a separate website on a subdomain sub.example.com. Would this possibly affect it?

Is there anything that stands out that would be doing this?

You wrote "www.example.com CNAME going to the cloudfront url."? What about `example.com`? Where does it point to? — Marcin, Feb 05 '21 at 01:28
When I try to add the example.com or *.example.com to the same cloudfront url, it won't let me enter it in saying invalid entry — uno, Feb 05 '21 at 01:29
I did attempt to remove the www.domain.com cname for the cloudfront url and use a wildcard, but it wouldn't load at all — uno, Feb 05 '21 at 01:30
Usually you would have to CNAMES. www.example.com->CF and example.com -> CF. Have you tried that? — Marcin, Feb 05 '21 at 01:31
Its not letting me do both? I'm on name.com. I just tried ANAME so we'll see how that goes — uno, Feb 05 '21 at 01:32
That's good :-). If you don't mind I will provide an answer. I — Marcin, Feb 05 '21 at 01:33

score 2 · Accepted Answer · answered Feb 05 '21 at 01:38

2

Based on the comments.

Resolution of example.com did not work because the DNS host (name.com) was set to resolve only www.example.com into CloudFront distro url.

The solution was to add ANAME record to point example.com into CloudFront distro url.

answered Feb 05 '21 at 01:38

Marcin

1 Answers1