UCC Cert issue with AD Top Level Domain

Hello,

I recently took over this organization and now installed a brand new exchange 2010 in a 2003 Active Directory forest domain. The issue that I noticed is that the DNS name space and NETBIOS name of active directory in this organization is called "domain.ad" and the external FQDN for the exchange is "mail.domain.com"

When I requested a UCC cert which includes the internal FQDN of the exchange server, the authentication failed as .ad is owned by the country Andorra. In order for me to get a .ad external domain the requirement is that you are a local resident for that country.

The question I have are the following:
1) I cannot rename the active directory dns name or netbios name with rendom.exe as there are too many services such as Microsoft Lync 2010 running in the organization
2) What is the recommended way that I get the UCC issued. Can I just add the NETBIOS names and for the external domain just create a split DNS?
3) The UCC i ordered is for 10 domains as I will be installing two more exchange servers in different sites, how would this impact the cert?

Any help would be appreciated.
LVL 2
bbwondersAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
MichaelVHConnect With a Mentor Commented:
Indeed, it's possible to not add the internal domain name, but in that case your internal clients could be presented with cert-warnings, which is indeed suboptimal.

About the names that you added: you still have to add e.g. autodiscover.domain.com.

To work around the issue of the local domain name for which you cannot request a URL, I suggest that you change the value of the internal URL's to match these of the external URL's. That way your clients won't be getting a cert warning. For more information take a look here:
http://support.microsoft.com/kb/940726/en-us

Grts,

Michael
0
 
Encrypted1024Commented:
Internal certs for Exchange and Lync (domain.ad) that only need to be trusted by your domain can be issued using Windows PKI. The 3rd party certs are only needed for your External namespace (mail.domain.com, lync.domain.com autodiscover.domian.com etc).

0
 
bbwondersAuthor Commented:
Thanks. I was reading some documentation that states to add the netbios name of the exchange CAS in the SAN. Can someone confirm if that's correct?
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
MichaelVHCommented:
bbwonders,

that is correct. There are some recommendations to keep in mind when using commercial certs.
Adding the netbios name is one of them (as internal users would likely approach the server using https://servername).

Greets,

Michael
0
 
bbwondersAuthor Commented:
So to make it correct, if i request a UCC with the following would it work with a split DNS lets say.

1) CAEX01
2) CAEX02
3) NYEX01
4) NYEX02
5) CACAS
6) NYCAS
7) Autodiscover
8) mail.domain.com
9) CAUM01
10) NYUM01

In this example the only external domain name i have used is the mail.domain.com, I have not used a internal FQDN of the machine. In my internal DNS zone, I can create a domain.com and add the CNAME records for a split DNS. Can someone confirm and I will request the SAN cert from GoDaddy
0
 
Encrypted1024Commented:
We have a legacy domain name that has a non certable internal DNS as well. We added only our external domain names to the cert. It is not optimal, but it works.

mail.domain.com
mail.other.com
mail.other.com
owa.domain.com
autodiscover.domain.com

We added all these subject alternate names to the cert.

The internal name of the mail server is not listed in the cert.
0
 
Encrypted1024Commented:
Just to add, I did not setup our current Exchange server, I was just mentioning that we have the exact same issue and have only the names listed in my previous post and do not get any cert errors on our clients. Not sure what was done to rectify this but it works without issues.
0
 
bbwondersAuthor Commented:
I think what Michael suggested is a good idea. That way i can do a split DNS and the internal users won't go out the network but still maintain the same name. Let me test today and get back to everyone.

Thanks!
H
0
 
bbwondersAuthor Commented:
Worked based on the recommendation. Thanks!
0
All Courses

From novice to tech pro — start learning today.