Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Out of curiosity: what's the reason behind this?

To be clear: I've checked a couple of root CA's websites while searching for an appropriate SSL Cert (that's another story). Every single one of them illustrates the usefullness of Multidomain Certs with MS Exchange Server's need.

share|improve this question
In future you might want to wait a while before accepting an answer to your question, maybe a day or two. – ThatGraemeGuy Feb 10 '11 at 20:33
up vote 2 down vote accepted

Usually because various application and naming conventions use different external names. Outlook RPC over HTTPS looks for, webmail usually points to, SMTP name might be presented like

share|improve this answer
Thanks, that sheds some light in the dark. But then again, this sounds like a perfect application for Wildcard Certs ... just wondering. – frombor Feb 10 '11 at 20:22
Well, not exactly. It very much depends what roles will do the Exchange server you're planning installing a certificate on. For example getting a wild card cert for a single-server scenario might require adding an external DNS zone along with the internal one. – Vick Vega Feb 10 '11 at 20:29
Wildcard certificates are not supported by some versions of Windows Mobile. While that may not be a concern now, at the time Exchange 2007 was released, it was, hence the official line was that a wildcard was not the way to do it. – ThatGraemeGuy Feb 10 '11 at 20:31
The good thing about wild card is that you can export it and install on any external server of the domain. Some customers found it valuable. – Vick Vega Feb 10 '11 at 20:34

Wildcard certificates are useful if you have many subdomains that you want to serve out.

Or you can have a SAN/UCC SSL Certificate from a third party for:
- exchange.yourdomain.local
- remote.yourdomain.local <-- VPN/RDP access.

With the new announcement that the coming IIS8 will support SNI (, this will probably change the way we apply certificates for exchange and everything else. In the future we could switch from using a Wildcard or UCC to using a single SSL cert for each SSL application we have, and a UCC one for Exchange.

More on SNI in IIS8:

IIS 8.0 support Server Name Indication (SNI), which has extended TLS to include the virtual domain name to be passed from the client at the time of "SSL Hello". This effectively allows IIS 8.0 to enable "hostname binding" for SSL sites, which eliminates the need for having a dedicated IPv4 address per SSL site.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.