Public DNS Exchange 2007/2013 Coexistence

Zee
Zee used Ask the Experts™
on
What should the public DNS be setup as for Exchange 2007/2013 coexistence.  I may be over thinking this but, do I adjust my firewall to point the existing IP to my EXCH2013?  I'm confused at this point.  I'm not sure how the additional public IP I setup comes into play.  currently I have mail.domain.com, legacy.domain.com, autodiscover.domain.com pointing to my Exchange 2007 server.  I added an IP for newmail.domain.com pointing to Exchange 2013.  I don't plan on using the name newmail but wanted it up there so I could have a placeholder.  I just don't understand how the new IP would come into play.  I would think I just adjust my firewall to point to my 2013 server.

Example of my public DNS:
mail.domain.com - 66.67.68.1
legacy.domain.com - 66.67.68.1
autodiscover.domain.com - 66.67.68.1
newmail.domain.com - 66.67.68.2

New setup?
mail.domain.com - 66.67.68.2
legacy.domain.com - 66.67.68.1
autodiscover.domain.com - 66.67.68.2
???
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Jose Gabriel Ortega CastroTop Rated Freelancer on MS Technologies
Awarded 2018
Distinguished Expert 2018

Commented:
HI Zee.
well you have your exchange server 2013, that's the latest version of exchange server.

So you already installed it, so just configure it.

So all your entry points should be pointed to your latest version of Exchange as a general rule.

So don't overthink and the Coexistence of the Exchange will take care of the communication between them.

https://secureinfra.blog/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration/

So...
If you don't plan to use newmail.domain.com...
you'd need to adjust the internal URLs on 2007 to match (legacy.domain.com)
and use on your exchange server 2013 the one that you want to use as final.
MaheshArchitect
Distinguished Expert 2018

Commented:
Point mail.domain.com and autodiscover.domain.com to exchange 2013 internally and externally - 1st public IP
Point legacy url to 2007 internally and externally - 2nd public IP
Exchange 2013 redirect traffic to 2007 url (legacy) when mailbox is on 2007 server
MASEE Solution Guide - Technical Dept Head
Most Valuable Expert 2017
Commented:
Here is a detailed article from Microsoft Technet.
https://blogs.technet.microsoft.com/meamcs/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration/
http://msexchangeguru.com/2013/05/10/exchange2013-migration/

You can use this to configure your Exchange2013 URLs and certificate.
https://www.experts-exchange.com/articles/29662/Exchange-2013-Fix-for-an-Invalid-certificate-and-related-issues.html

Use this to generate command for CSR. Refer Above article for the name requirements.
https://www.experts-exchange.com/articles/28662/Easy-CSR-creation-Exchange-2007-2010-and-2013.html

As commented above after configuring all these point common name and autodiscover to 2013.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

ZeeIT Manager

Author

Commented:
Thank you Jose, but I've already used that article to do my installation along with various other sites.  I'm all set with everything except for the cert and external dns.
ZeeIT Manager

Author

Commented:
Mahesh, thank you for this info.  I'm sorry if you answered this in your comment but should I change my newmail.domain.com to the mail.domain.com IP address?  Then set legacy.domain.com to the IP I set for newmail and then adjust my firewall?
ZeeIT Manager

Author

Commented:
MAS, thank you. I've seen both of the first 2 articles and already have my URLs all setup.  All I need is to understand/setup my external IPs.  I'm lost as to how the new external IP comes into play. I'm beginning to think I just adjust my firewall and set legacy to newmail.domain.com IP.
ZeeIT Manager

Author

Commented:
Ok, so I just adjusted my public DNS.

mail.domain.com > Exchange 13
autodiscover.domain.com > Exchange 13
legacy.domain.com Exchange > 07

I thought it would be easier to go at this from the firewall route but may be overthinking it.  So I went the public DNS route...
EE Solution Guide - Technical Dept Head
Most Valuable Expert 2017
Commented:
Above is correct.
1. Configure legacy.domain.com URLs in Exchange 2007.
2. Point your legacy.domain.com to exchange 2007 (internal DNS and external DNS).
3. Point your mail.domain.com (common name) to exchange 2013 (internal DNS and external DNS).
4. Point your autodiscover.domain.com (common name) to exchange 2013 (internal DNS and external DNS).
ZeeIT Manager

Author

Commented:
Thank you for confirming MAS.  Thank you all for responding so quickly.  I just tested my changes and I am all set.
MASEE Solution Guide - Technical Dept Head
Most Valuable Expert 2017

Commented:
Glad to know we could help. :))
ZeeIT Manager

Author

Commented:
After my changes mail was getting stuck in my 2013 queue.  Turns out I had to create a receive connector to allow the internal relaying to happened.  Not sure how I missed that but I'm not seeing it in the steps outlined by Microsoft for 2013/2007 coexistence.

https://community.spiceworks.com/topic/1923259-internal-mail-flow-getting-stuck-in-queue-exchange-2013-and-2007-coexistence
https://docs.microsoft.com/en-us/Exchange/mail-flow/connectors/allow-anonymous-relay?view=exchserver-2019

In case anyone else runs into this problem.  I'm all set now with the 2 servers running and mail flowing.  Time to relax and BBQ, lol.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial