Announcement

Collapse
No announcement yet.

One MX with each Exchange Site

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • One MX with each Exchange Site

    Hello Everyone,

    Wanted to validate my thinking around this. Right now, I have one Exchange site with all users mailbox and only one MX record.

    I want to add another Exchange site (additional domain in same forrest) and I will be moving some mailboxes over to this site.

    Outgoing mail will go out their respective Exchange server. I want to add a new MX record for incoming mail on the second site.

    If mail comes in on one MX, if the mail is destined for a mailbox on the other server, it will just traverse through the site to that server, true? Any issues?

    Thanks...BirdDog

  • #2
    Re: One MX with each Exchange Site

    Email can hit any server in the Exchange org. Once Exchange has the email message it will deal with delivery to the correct server.
    If a site has two or more Exchange servers in two different locations then I actually encourage the use of two MX records to provide a backup route in. However you need to ensure that both MX record servers are well protected with AV and Antispam - not just what you would consider to be the primary.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: One MX with each Exchange Site

      Sembee,

      Perfect response. You are 100% crystal clear and this is what I just needed to validate for myself.

      Thank You!

      Thanks...BirdDog

      Comment


      • #4
        Re: One MX with each Exchange Site

        Just another tip for Exchange multi-site message routing: I've been working on expanding a companies Exchange infastructure, and now have a total of five seperate sites, each with it's own child domain and exchange server. What we've found is that Exchange uses the MX record for routing all the messages. The problem we had is the customer has a sprint MPLS network, which won't allow traffc from "site a" to go out the firewall and back in to go to "site b", thus causing inter-site messaging to stop funcioning (the servers where resolving to the public MX). What we did was add host entries on the exchange servers of the sites with the MX address of the other sites pointing at the private address of the sites exchange server. This could also be done using DNS.

        Comment


        • #5
          Re: One MX with each Exchange Site

          If your Exchange deployment is using MX records then something is wrong with your deployment.
          If all of the servers are in the same Exchange org then MX records should ahve nothing to do with it. Exchange will simply send the email internally. It goes by SMTP and DNS is important - but that is internal DNS, not external. MX records are not used by Exchange for internal email flow, even when you are using child or sub domains.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment

          Working...
          X