Link to home
Create AccountLog in
Avatar of m4dd0g
m4dd0gFlag for Israel

asked on

Exchange 2010 SP2 multi tenant, SSL certificate per domain

Hello,
We have a multi tenant Exchange 2010 SP2 system, we're hosting multiple clients, each client has its down domain. For example: client1 -> domain1.com & client2 -> domain2.com

Currently each client access OWA via our main domain: https://exchange.mycompany.com/owa
Each customer can configure his Outlook using our mail domain: exchange.mycompany.com
or using its own domain mail.domain1.com or mail.domain2.com.

One of my customers told me that he is getting certificate warnings from Outlook, he has his domain configured as exchange server: mail.domain1.com and the warnings are coming about his domain.

Our main domain has an SSL certificate installed, I can see it's working in the Exchange Console and also our IIS OWA is protected.

How can I install a separate SSL certificate for each customer? I have bough a wildcard SSL for him *.domain1.com and I want to use it so he will stop receiving this alerts.

Thank you.
ASKER CERTIFIED SOLUTION
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of m4dd0g

ASKER

Thanks, is it possible to exclude a record from * wildcard record in dns zone ?
No. There is no such thing as an exclusion in DNS.
The wildcard must be removed. The closest you can get is to blackhole autodiscover (So set it to 127.0.0.2) but that can cause problems with Outlook clients so it isn't a recommended path.

There should be no need for a wildcard in DNS - it is just laziness from hosting companies.

Simon.
Avatar of m4dd0g

ASKER

the clients keep receiving the message after disabling the autodiscover,
the warning they receive is:
"the certificate cn name does not match the passed value"
"Do you want to continue using this server?"

thanks for help.
You need to look at the certificate to see where it is coming from. Their DNS is obviously not setup correctly.

Simon.
Simon Butler you are a wise man.

I like to ship in a couple of my own tips.

Sometimes, we folks who do multi tenant Exchange hosting do not have the luxury of managing the DNS for the client's domain, we have no say if they do a wildcard host name, only the MX records are pointing to our system.  The way we overcome DNS problems when someone else manages it, is as followed:

Make sure the autodiscover feature of the primary domain (exchange.mycompany.com) is working properly, since all the tenant domains rely on the primary domain's SSL certificate.  In particular, make sure the SRV record for the primary domain is fully spelled out, i.e _autodiscover, _tcp, 0,0,443, SSL name.  

If an incorrect client domain autodiscover record is causing error with your SSL certificate, as in the above example, when autodiscover.clientdomain.com does not match the name of the certificate, namely exchange.mycompany.com, then we simply block the host name by adding 127.0.0.2 to autodiscover.clientdomain.com on the client's PC "hosts" file.  This will eliminate the certificate pop up error.