Link to home
Start Free TrialLog in
Avatar of tp-it-team
tp-it-team

asked on

Migrating from 2007 to 2013 - legacy.domain.com question

Hi !

Can someone explain me in simple words the importance of creating legacy.domain.com for the old 2007 server ?
While I can understand why it's required for internal DNS, I don't understand the external one...

After redirecting the mail traffic to a new server on my firewall, while still having mailboxes on 2007, I thought it will work like this:

Client connects to mail.domain.com (new 2013 server) -> 2013 is looking for legacy.domain.com 2007 internally and gets the data from there.

Why do I need external legacy dns entry, especially that it will point at exactly the same IP ?
SOLUTION
Avatar of M A
M A
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tp-it-team
tp-it-team

ASKER

Exactly, so why will I need external legacy.domain.com DNS ?
My clients will connect to 2013 and it will resolve the old 2007 INTERNALLY by using legacy.domain.com
-->Exactly, so why will I need external legacy.domain.com DNS ?
Your Exchange2007 users will connect to Exchange2013 and it will redirect to Exchange2007 server both internally and externally using name legacy.domain.com
Why would I need external redirection if my both servers are behind one external IP ?

Sorry to be stubborn, but I cant digest the fact that I need additional EXTERNAL IP to migrate from 2007 to 2013...
When your external clients redirected to legacy.domain.com it should be resolved to an IP
both internally and externally
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial