How important is the Legacy DNS with 2003/2010 migration 1

[mlchris2]

Im preparing to do the final transition steps of a 2003/2010 upgrade and place the 2010 server public facing. In reading a transition guide, it states that I should create a public and private DNS record "legacy" and point it to the exch 2003 server... blah blah blah.

Well, my public DNS structure for email is a single IP... is this just a recommendation or is it something I really need to do?

I plan on testing all connectivity once I put the exch2010 server public and then move everyone over to the new server. So I'm thinking I shouldn't need the legacy dns on the public side, maybe just internally if anything.

can someone offer some insight?



Mark C.

 

[58sniper]

The legacy requirement is there if you're going to have users who have mailboxes on 2003 trying to log on via OWA on 2010.

If your plan is to make 2010 public facing and immediately migrate the remaining users to 2010 (so none will require access to 2003 mailboxes), you *should* be ok. It's only the part of coexistence that requires it.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[mlchris2]

Sniper you are correct, I found out the hard way yesterday. Even though in the transition guides from Microsoft, it's just a recommendation, but it is a necessity if one is SLOWLY transitioning from exchange 2003.




Mark C.