[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More


Additional Domain for Exchange 2010

Published on
25,048 Points
19 Endorsements
Last Modified:
Community Pick
For many reasons it can be necessary to configure an Exchange Server to receive and send mail for an additional domain name.  You could be changing domains, adding an additional trading name for our company or simply merging with another organisation.  Or like me and other IT Consultants you could be hosting your own Exchange Server and providing your customers with access to hosted Exchange as part of your service.

This guide will give you all the details required to configure your Exchange Server to send and receive for an additional domain.  Correctly!

Step 1 – DNS

DNS is an important requirement when it comes to configuring any e-mail server to send/receive email, not just Exchange.  More and more companies are checking for correctly configured DNS to verify that you are who you say you are and to evaluate whether to accept your emails or not.

I am not going to cover the primary DNS configuration in detail as it’s covered in my article here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2370-Exchange-DNS-Configuration.html

However, as long as you have your primary sending Domain Configured correctly, ie:
A Record = mail.domain1.com which is set to your Exchange Servers external IP address
MX Record for domain1.com = mail.domain1.com
rDNS record = mail.domain1.com

Notice they all match? This is important.  Some anti-SPAM solutions will check this.

So how do we accept email for another domain name?  It’s surprisingly easy, as long as the above is configured properly then all we need to do is create a new MX record in domain2.com DNS and configure it to use the A record mail.domain1.com.

The reason for this is because you can only send out of your network using a single IP address (this is a limitation of most routers/firewalls).  When the receiving mail server receives your email it will check the header information to see where it came from, and then do a reverse lookup to confirm that the IP address is valid/not on a blacklist/not dynamic (in a lot more cases) and has a valid rDNS entry.

So just because you are sending an email from an additional domain doesn’t mean you have to add another entry to your rDNS, this will just confuse the issue and cause false positives on SPAM systems.  Keep it simple.

Step 2 – Accepted Domain

Now that we have our DNS configured correctly we need to tell Exchange that it is allowed to accept mail for this domain.  To do this using the Exchange Management Console navigate to Organisation Configuration > Hub transport.  In the Actions pane on the right hand side select New Accepted Domain.  This will start the wizard (screen shot below).
 Additional-Domain-01.jpgThe name of the Accepted Domain doesn’t matter; this is just a descriptive comment to help you identify it easier.  Enter a name and then an Accepted Domain; this is the actual domain name that you want Exchange to receive mail for.  Then click New and Finish.

That’s it, Exchange will now receive mail for that domain, however, until we setup some recipients to receive for that domain mail will be rejected as recipient unknown.

Step 3 – Recipient configuration

The next step of configuration is to setup an email address policy and create mailboxes with the correct email addresses.

My preferred method of achieving this is to create the users in a separate OU within Active Directory and applying the Address Policy to this container.  This ensures that when you create a new mailbox and place the user in this container it will be given the correct address information.

Using Exchange Management Console, navigate to Organisation Configuration > Hub Transport and in the Action pane on the right select New e-mail Address Policy.  This will start the wizard as shown below.
 Additional-Domain-02.jpgEnter a name and select the OU using the browse button where you will place the users.  Then click Next.  On the following screen (shown below) we have the choice to enter a particular value to search on the users to evaluate the email address policy.  As we are placing the mailboxes in an OU of their own we don’t need to worry about this screen.  Just click Next.
 Additional-Domain-03.jpgOn the next screen we specify the email address we want to apply to these mailboxes.  Click the Add button and then select the domain and the format of the email address (as shown below).  Once done click OK and then Next.  Click next and then New to finish the wizard.

Step 4 – New Mailboxes

The final stage of the process is to create the new mailboxes.  Now that we have everything else in place this bit should be very straight forward.

Using the Exchange Management Console, navigate to Recipient Configuration and Mailbox.  In the Action Pane on the right hand side select New Mailbox.  On the first screen select User Mailbox and click Next.  Select New User and click Next.

The following screen (image below) is where we enter the details of our new user.  Importantly we need to use the browse button to select the Organisational Unit where our new user will be placed.
 Additional-Domain-05.jpgOnce done click Next.  On the following screen specify the Alias of the user and if required any policies you have configured along with a different mailbox store if you are keeping these users in a different database.  Once done click Next and then Next again and new to finish the process off.

Step 5 – Checking the detail

Now that’s all done it’s always nice just to check your work and confirm the recipient is configured correctly.

To do this right click on your newly created user and select properties.   Under the email addresses tab (image below) you should see the email address created manually for your new domain in the format you specified in Step 3.
If you liked this article and want to see more from this author, please click the Yes button near the:
      Was this article helpful?
label that is just below and to the right of this text.   Thanks!

Written by Glen Knight (demazter) as part of a series of how-to articles.  
Author:Glen Knight
LVL 76

Expert Comment

by:Alan Hardisty
Great article - yes vote from me :)
LVL 38

Expert Comment

I wish you had been around when I was an Exchange Administrator - wudda made my job a whole lot easier.

"Yes" vote above.

Expert Comment

I am trying to add a new accepted domain, but the "New Accepted Domain" is not available.  How do I resolve this issue?  I am including a screenshot

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.


Expert Comment

But you don't mention that in this configuration, everyone will have access to the global OAB, meaning the customers can see other customers, as well as your own organisation?
LVL 74

Author Comment

by:Glen Knight
I don't mention it because at no stage did I say this was a multi-tenant solution.

Until SP2 (or Hosting Mode) Exchange 2010 didn't support multi-tenant or address list segregation.

That is not the intended purpose of this article!

Expert Comment

How do you do this if you want to use an existing user in the AD, and when they open outlook they will see both domain mailboxes.

Also need the reply email address to be the same as the domain the email was sent to

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Please check the video also in regards to recovery of deleted emails from office 365 admin center and through the MFCMAPI tool. I have mentioned each and every step with the proper steps that need to be taken care of.

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month