UCC Cert issue with AD Top Level Domain

Posted on 2011-02-27
Last Modified: 2012-05-11

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 "" and the external FQDN for the exchange is ""

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.
Question by:bbwonders
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
LVL 10

Expert Comment

ID: 34992758
Internal certs for Exchange and Lync ( 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 (, etc).


Author Comment

ID: 34992772
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?
LVL 11

Expert Comment

ID: 34992975

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).


Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.


Author Comment

ID: 34993099
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
7) Autodiscover
9) CAUM01
10) NYUM01

In this example the only external domain name i have used is the, I have not used a internal FQDN of the machine. In my internal DNS zone, I can create a and add the CNAME records for a split DNS. Can someone confirm and I will request the SAN cert from GoDaddy
LVL 10

Expert Comment

ID: 34993428
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.

We added all these subject alternate names to the cert.

The internal name of the mail server is not listed in the cert.
LVL 11

Accepted Solution

MichaelVH earned 125 total points
ID: 34994996
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.

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:


LVL 10

Expert Comment

ID: 34999528
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.

Author Comment

ID: 34999815
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.


Author Closing Comment

ID: 35130970
Worked based on the recommendation. Thanks!

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to:…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Suggested Courses

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question