To continue reading for free, register below or login
To read more you must become a member of SearchExchange.com
VIEW MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A.
It is possible to use DDNS. However, the certificate's common name must match the fully qualified domain name (FQDN) you use with DDNS. Using the IP address will not work unless the common name of the certificate is the IP address.
By the way, there are varying degrees of the word "works" when it comes to Web server certificates. The first level is to establish an SSL session. The next level is to get it to work without any certificate errors. The most common error is that you are not using a "Trusted CA." If this is the error you are getting, then you can simply publish the Root Certificate so that users can import it into their Web browser's trust list. If these are Active Directory (AD) members, I would recommend using a Group Policy Object (GPO) to perform this task.
MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A:
Depending on your purpose, there is a way to possibly accomplish this. I support Windows Small Business Server (SBS). Several clients have Windows Mobile phones that "require" a Root level certificate, but self-signed certificates created by SBS are not Root level.
—Kevin K.
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:
Expert Advice: How enabling SSL for OWA affects bandwidth
Expert Advice: Securing a front-end certificate server
Tutorial: How to set up a front-end Exchange Server cluster
Tip: ActiveSync and front-end DNS aliases
Reference Center: Exchange Server authentication resources
|
