Exchange Routing Between Subdomains

Posted on 2007-10-02
Last Modified: 2010-05-18
Exchange Routing Question:

Current Environment:
I currently have a windows 2003 domain and an Exchange 2003 environment.  This environment is setup to receive email from  The MX records for this domain point to Microsoft Hosted Exchange which then routes the emails to our Exchange servers.  The internal DNS name for this organization is NOT

New Environment:
In order to support a different business unit within our organization we are setting up a parallel network.  That means a new Active Directory forest, new routers, switches, etc.  This also includes a new Exchange 2007 environment.  These two setups will be completely separate and they will not have any direct connectivity between them.  We are setting them up for SOCKS reasons and do not have a choice on the setup.  This is how it has to be.  The internal DNS name for this organization should be

Email Routing:
The idea, if we can make it work, is to setup both domains to be able to receive email with the same primary dns suffix.  What I mean by that is if I email then the email gets delivered to the current Exchange Org.  If I email a subdomin ( then the email gets delivered to the new org.  This can be easily accomplished using subdomain MX records and Microsoft Hosted Exchange to route the emails to the correct external IPs of the 2 different orgs.

The problem I see in this is routing between the orgs.  If I am sitting in the new domain and my email address is  and I email   the Exchange server is going to look inside its own organization for, not find it and have issues.  The same will be true if I am sitting in the old org and try to email someone in the new org.

Now I am pretty sure that there is a way to get around this routing and to have the two orgs forward emails to the other org based on the subdomain.  What I am not sure of is how to do this.  Can anyone tell me?
Question by:brownmattc
    1 Comment
    LVL 104

    Accepted Solution

    The sub domain is the key here.
    Put a sub domain on to each domain, even though the one on the primary will not be used outside.
    The use SMTP Connectors (E2003) or Send Connectors (E2007) to route email for the sub domain directly. That will mean port 25 being open between the two networks, but you need that otherwise routing of the email will be a mess.

    Then use mail enabled contacts for users in the other domain, with the primary address being the sub domain. On the E2003 server, add the main domain as well, so the contact has both addresses and and it will serve as the routing point for external email as well.
    Now I don't know if the email address forwarding trick works on E2007, I haven't tested it yet. If I get a chance I may do later in the week.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Use email signature images to promote corporate certifications and industry awards.
    Use these top 10 tips to master the art of email signature design. Create an email signature design that will easily wow recipients, promote your brand and highlight your professionalism.
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
    This video discusses moving either the default database or any database to a new volume.

    737 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

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now