Steps to add a domain to Exchange
I host several domains on my server, including dpotter.net. Recently I added another domain for a friend who is starting her own business. I thought I remembered all the steps to provide both web site service and email service, but there was one I missed that I don’t remember being a requirement before.
For background, I’m running Microsoft Small Business Server 2003 with IIS 6 and Exchange Server 2003. My box is also a domain controller, a DHCP server, a DNS server, an RRAS server, and a few other servers to boot.
First let me describe what I ran into and then I’ll list the steps I use to add a domain. I added the domain so that Exchange could recognize it, added a user with a mailbox for my friend, and set up my spam filter (Exchange Hosted Services, aka Frontbridge) to allow traffic to the new domain to pass through it successfully. However, whenever I tried to send email to the new user from an outside mailbox, I would get the following non-delivery report:
Unable to relay for (in reply to RCPT TO command)
After much hair-pulling and Internet searching, I ran across an article titled Multiple Email Domains on Exchange 2K3 - Relay Access Denied by James Montgomery. It spelled out the extra step I had to take - update the IIS Metabase. Huh? I’d never had to do that before. But it worked, so I’m a happy camper again.
Note that to modify the IIS Metabase you’ll have to download and install the IIS 6 Resource Kit.
Adding a domain
- Add the domain to Active Directory as a UPN suffix. This will allow you to add users that can log in using the new domain.
- Run the Active Directory Domains and Trusts management tool from Administrative Tools (domain.msc).
- View properties of the root node in the console (titled Active Directory Domains and Trusts).
- Add the new domain and click the Add button.
- Add a new domain to the set of Internet message formats in Exchange System Manager.
- Run the Exchange System Manager tool from Administrative Tools.
- Open Global Settings.
- Right-click on Internet Message Formats, click New, then click Domain.
- Type the name of the domain in both the Name and SMTP domain fields.
- Click OK.
- Add a recipient policy for the new domain.
- Run the Exchange System Manager tool from Administrative Tools.
- Open Recipients.
- Right-click on Recipient Policies, click New, then click Recipient Policy.
- Select E-Mail Addresses and click OK.
- Type the name of the new domain in the Name field.
- Switch to the E-Mail Addresses (Policy) tab.
- Create a new smtp policy for the new domain.
- Click New and select SMTP Address.
- Type the name of the new domain with an at-sign before it (e.g. @mydomain.com) and click OK.
- Add the domain to the IIS Metabase.
- You may want to perform a backup of your metabase before proceeding.
- Open MBExplorer from the IIS 5 Resource Kit.
- Navigate to
LM\SmtpSvc\1\Domain\. - If the new domain is not in the list (which is probably will not be), add a key for the new domain.
- Right-click one of the other domains and click Copy.
- Right-click Domain and click Paste.
- Select Copy to a new key.
- Type the new domain name and click OK.
- Run the iisreset tool to reset IIS (click Start » Run, type
iisreset, and press Enter).
Now you can create users that use the new domain in Active Directory Users and Computers and you can create web sites that use the new domain in IIS Manager.




March 26th, 2009 at 2:48 am
I can’t believe I hit this again and didn’t even look at my own site! What a pain it is to add domains. I wonder if Exchange 2007 solves this management problem.
August 21st, 2009 at 11:20 am
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you! A thousand times thank you! We just migrated to Exchange 2003 and this error was driving me crazy. Not a single site nor book had the answer until I stumbled upon your site. Thank you and thank you again.
September 15th, 2009 at 8:02 am
Hi David,
I’m having a related issue in that I am using Exchange 2003 that is receiving all mail for my domain, which is pointed in DNS on my webhost directly to the Public IP of my email server. The website, with is also the same domain name, would try to resolve to localhost, so I had to specify an entry for the mail domain in question in CPanel. I checked DNS from CPanel and saw it resolving correctly. I also created a specific port 26 for SMTP on my email server and poked a hole for that port in my firewall. I can reach SMTP through a command line no problem, but Mailpress fails everytime with a Connection Timeout: The SMTP connection failed to start [xxxxxxxxxxx.com:26]: fsockopen returned Error Number 110 and Error String ‘Connection timed out’
Got any ideas?
Thanks!
Vince