Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

From previous advice I've created my Domain Controller (2008R2) with a mydomain.local name (instead of, split DNS scenario) So my users have logins like admin@mydomain.local. And for logging in to the servers that fine I guess.

Now on the Same domain I've installed a Exchange 2010 server. (with client access External domain pointing to our public After install I see that my domain admin is imported and has its own mailbox. When I look at the details I see for email: admin@mydomain.local.

Of course this makes sense but its not what I'm looking for. The mailserver should be serving the public .com domain and it would be nice if users can enter with their .com adres and credentials.

So the question is can I configure this and where should I do this to make it work for all new users I import from AD.

For the record I'm still in a test environment. In their I've created forward lookup zone for so I'm able to test all public domain stuff offline before I migrate.

share|improve this question
There's no such thing as PDC/BDC any more. A Domain Controller can hold the PDC Emulator FSMO role, but it's not the same as being a PDC from the NT4 days. – MDMarra Jun 7 '12 at 20:18
Thanks not sure what you mean but I meant with PDC my Primary Domain Controller I will rephrase my question – Joost Verdaasdonk Jun 7 '12 at 20:25
There are no primary domain controllers any more. There haven't been since Windows 2000 Server was released. All DCs are multi-master peers. – MDMarra Jun 7 '12 at 20:26
Ok changed my question thanks – Joost Verdaasdonk Jun 7 '12 at 20:28
By the way. You shouldn't use .local if you can help it. To avoid split-horizon DNS situations use a non-public third-level domain for your AD. Example: – MDMarra Jun 7 '12 at 21:04
up vote 3 down vote accepted

There are two parts to this you need to hash out:

1) You will need to add the .com domain in Exchange setup as a domain that it is responsible for and set up the policies and whatnot to distribute those as the primary sending domain for your users.

2) Somewhere in one of the AD snap-ins, I cannot remember if it's domains and trusts or users and computers, you can define additional user principle names, so that your users can login as OR user@domain.local. You can then specify the primary per user.

Just keep in mind, the mail handling of domains and the user login handling of domains is each a different animal.

share|improve this answer
Ok thanks for the ideas I will first try to read up on the pointers you gave me and report back if I have problems. – Joost Verdaasdonk Jun 7 '12 at 20:30
@Zoredache thanks that helps. Already found: going to read them both and try it out – Joost Verdaasdonk Jun 7 '12 at 20:38
It is in fact in Active Directory Domains and Trusts where you add additional UPN suffixes. – joeqwerty Jun 7 '12 at 20:46
Ok changed the accepted domain and edited default email policy to include the new domain so now all mails are updated. Not sure if it all works but I'll test that later. Ah nice tip Joe! Ok I will go and find that UPN stuff now. – Joost Verdaasdonk Jun 7 '12 at 20:55

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.