Hello out there. I've received the following e-mail from GoDaddy at the bottom of my post (I've slightly changed the common name of the cert to a bogus name for security purposes). GoDaddy will revoke the certificate by October 1st unless I update the common name to a FQDN. I'm going to test this on a non production virtual machine, but I still wanted to put a few questions out to the folks out there on the interwebs.
1. My server's computer name is currently the same as the common name of my certificate. I've read this must so, or the encryption will not work. Can I simply change the name of the server itself (computer name in Server 2008 R2 ) to www.abc.com from ABCSQL.companyname.local without any repercussions?
2. I have several different websites accessing this SQL server from different domain names. Can I choose any one of my domain names? For example if I choose www.abc.com as the common cert name for SQL, will www.xyz.com still be able to access the DB?
3. Right now I am not forcing encryption. Anyone out there have an opinion on this setting?
4. As of now, the certificate is not available in the drop down list of the SQL Server Configuration Manager under SQL Server Network Configuration. I've read this is because the certificate must use a FQDN. Has anyone else experienced this issue?
I have two SQL servers at the moment. Both are Windows 2008 R2. One is running SQL Server 2008 and the other is running SQL Server 2012. Thanks for reading and thank you for any input you can provide.
***Email from GoDaddy below***
An SSL certificate's common name is the primary domain name it secures/encrypts. Because your common name is an internal name or IP address, your certificate is no longer valid. This applies to the certificate for the following domain name(s):ABCSQL.companyname.local
Please change your common name to an FQDN before September 28, 2016. If you don't make this update, we're required to revoke your certificate by October 1, 2016.