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.
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.
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:
Dig deeper on Outlook Web Access
Related Q&A from Richard Luckett
There are a number of actions to take to implement OWA security, including obvious ones like creating strong password policies. Admins should also ...continue reading
Our resident Microsoft Lync expert explains where to find IP phones that are compatible with Microsoft Lync Server.continue reading
While Cisco IP phones are not directly compatible with Microsoft Lync Server, there are ways to make them compatible. Lync guru Richard Luckett ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.