Author Topic: Why SSL Doesn't work with WWW version of Website?  (Read 1185 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Why SSL Doesn't work with WWW version of Website?
« on: January 07, 2023, 06:27:08 PM »
Hello,
My websites works OK with non-WWW address, but when I open them with "www" prefix I always get SSL warning in browser.
Anyone else have same issue?

Here are some examples:
https://www.theeasttravel.com  (show warning in Browser)
https://theeasttravel.com          (without www SSL Works Fine)

https://www.wonderfulsearch.com/   (show warning in Browser)
https://wonderfulsearch.com/           (without www SSL Works Fine)

How can I fix this? any help please? :-\


Offline
***
Re: Why SSL Doesn't work with WWW version of Website?
« Reply #1 on: January 08, 2023, 07:53:35 AM »
www IN A ip.ip.ip.ip
or
www IN CNAME @
or
* IN CNAME @

Offline
****
Re: Why SSL Doesn't work with WWW version of Website?
« Reply #2 on: January 29, 2023, 11:57:06 PM »
The difference between an A record vs CNAME is an extra DNS lookup. In case of the CNAME the after figuring out that www is a CNAME to example.com, another look will be done for example.com.

If you are planning on using a CDN or a 3 party acceleration service (Cloudflare), then a CNAME becomes important. Example a lookup of www.google.com results in the following. See the difference in TTL of www.l.google.com and www.google.com:

Code: [Select]
www.google.com.     36545   IN  CNAME   www.l.google.com.
www.l.google.com.   294     IN  A       209.85.153.104
This gives the flexibility of changing the A record, keeping a lower TTL, doing fancy stuff like geo-redirection, if using 3rd party services.

In this case, it doesn't matter since both are pointing both to the same IP (domain=www) -- as is commonly the case with smaller sites.