25 Feb
2013
25 Feb
'13
6:42 p.m.
On Feb 25, 2013, at 10:01 AM, Patrick Lists wrote:
On 02/25/2013 06:24 PM, Les Mikesell wrote: [snip]
I think the only clean approach is to give domain.com an A record pointing to something that can run a web server that does a client redirect to www.domain.com. And even then https will show an invalid cert before the redirect unless you have one specifically for domain.com.
Afaik that can be solved by adding a subjectAltName to the cert so it's valid for domain.com and www.domain.com and it's FQDN. Or maybe get a wildcard cert.
Regards, Patrick
Sorry I should have clarified.
The SSL is a wild card cert with a SNA of *.domain.com and domain.com
- aurf