I have an WinSBS server that resides behind a firewall with a 192.168.1.x address. The external hostname is remote.server.com, which port forwards email and IIS. Recently, the company changed the external hostname to email.newhost.com.
When it came time to renew the SSL certificates for Exchange/IIS, a new SSL cert was created using the new hostname. Although the certificate successfully installed, none of the services (POP, IMAP, IIS, SMTP) bound to the new cert. They are still bound to the old cert, which uses the old hostname.
I believe this is related to the external hostname switch over, but am not sure how to resolve it. Will either of the following resolve the issue?
1) Add email.newhost.com to the server's DNS so that email.newhost.com will resolve as the server's 192.168.1.x iP
2) Have a new SSL certificate issued, and add remote.server.com as a legacy domain