In my Windows network I have two Edge Transport Servers running Exchange 2010. They are currently configured to send and receive email using @mycompany.com
Currently I have MX records set up for @mycompany.com pointing to my two Edge Transport Servers; ETS1.mycompany.com and ETS2.mycompany.com
My A records for ETS1.mycompany.com and ETS2.mycompany.com point to the respective IP's of the edge transport servers.
I now have a requirement to also send and receive emails using @othercompany.com
I have registered @othercompany.com and am now trying to figure out how to set up the MX and A records for this new domain.
Should I configure them to point to ETS1.othercompany.com and ETS2.othercompany.com and then set the A records for ETS1.othercompany.com and ETS2.othercompany.com to the IP addresses of each edge transport server?
Will it be a problem if two different MX records resolve to the same IP address, or that one IP address will resolve to two different MX records for two different domains?
My edge transport servers are not on my domain (they're in the DMZ) but I didn't configure them when they were first installed so they're a bit of a black hole in my knowledge; is there anything I should be aware of in their regards?
Thanks for reading.
Best Answer Mordkanin , 27 March 2013 - 18:33
No it's not a problem to have two diff. domains with their MX record pointing to the same IPs. What you will need to do tho is tell Exchange that it will start processing messages from this new domain and set up the user mailboxes appropriately. Unfortunately I don't have an exchange machine locally so I can't help you out with the configuration settings, but if I am not mistaken, it's something related to the delivery policies.
Organization Configuration -> Hub Transport -> Accepted Domains Go to the full post