DNS Records for exchange 2003/2010 coexistence
I need to understand the records that must be included in internal / External DNS for Exchange 2003/2010 Coexistence please explain why they are in the internal and/or in the external DNS
I have done a lot of reading, and they recommend having, mail.domain.com, legacy.domain.com,autodisc
any expert out there that have configured DNS for exchange 2003 and exchange 2010 coexistence...please explain which records you put in the public and internal DNS, and why you needed these records and how they are touched during mail flow and access
Thank you
I have done a lot of reading, and they recommend having, mail.domain.com, legacy.domain.com,autodisc
any expert out there that have configured DNS for exchange 2003 and exchange 2010 coexistence...please explain which records you put in the public and internal DNS, and why you needed these records and how they are touched during mail flow and access
Thank you
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Internally they will get the internal IP address, externally they will get the external IP address.
There is no way that the external users will get the internal IP address of the legacy address because OWA just tells the client to go somewhere else. It is down to the client to resolve the address, not Exchange.
Simon.
There is no way that the external users will get the internal IP address of the legacy address because OWA just tells the client to go somewhere else. It is down to the client to resolve the address, not Exchange.
Simon.
ASKER
Hi Sembee2:
Ok, Briefly :
the external user will type https://mail.domain.com, then username and password, the request will be redirected to the public IP address of the firewall, since it is an SMTP request, it will be NATted or redirected to the internal IP address of the CAS server, which in turns will look for the mailbox location in Exchange servers...
At this point if the mailbox is in Exchange 2003 server, will the CAS redirect the request to the IP address of Legacy.domain.com record located in the internal DNS server, which should be pointing to the Front End Server OR to the IP address of Legacy.com record located in the public DNS server ?
it will make sense that it will be redirected to the internal IP address of the Legacy.com record located in the internal DNS pointing to the FE, since it is closer instead of redirecting it to the IP address of Legacy.com located in the public DNS, then coming back to the Front End Server
Ok, Briefly :
the external user will type https://mail.domain.com, then username and password, the request will be redirected to the public IP address of the firewall, since it is an SMTP request, it will be NATted or redirected to the internal IP address of the CAS server, which in turns will look for the mailbox location in Exchange servers...
At this point if the mailbox is in Exchange 2003 server, will the CAS redirect the request to the IP address of Legacy.domain.com record located in the internal DNS server, which should be pointing to the Front End Server OR to the IP address of Legacy.com record located in the public DNS server ?
it will make sense that it will be redirected to the internal IP address of the Legacy.com record located in the internal DNS pointing to the FE, since it is closer instead of redirecting it to the IP address of Legacy.com located in the public DNS, then coming back to the Front End Server
Why would it use the internal IP address?
Client hits mail.example.com, which is the Exchange 2010 server. The user logs in. Exchange sees that the user is a legacy mailbox so redirects the user to legacy.example.com - this is basically a HTTP request. The client (browser) then does a regular lookup of legacy.example.com and goes to that IP address. If external then it will be a query against your external IP address. You just need to ensure that you are pointing the NAT for the external IP address for legacy.example.com to the Exchange 2003 platform.
Simon.
Client hits mail.example.com, which is the Exchange 2010 server. The user logs in. Exchange sees that the user is a legacy mailbox so redirects the user to legacy.example.com - this is basically a HTTP request. The client (browser) then does a regular lookup of legacy.example.com and goes to that IP address. If external then it will be a query against your external IP address. You just need to ensure that you are pointing the NAT for the external IP address for legacy.example.com to the Exchange 2003 platform.
Simon.
ASKER
<<Client hits mail.example.com, which is the Exchange 2010 server. The user logs in. Exchange sees that the user is a legacy mailbox so redirects the user to legacy.example.com - this is basically a HTTP request>>
Ok, that's when the user is inside the network and trying to use OWA. the legacy.example.com here should be pointing to FE
==========================
<<If external then it will be a query against your external IP address. You just need to ensure that you are pointing the NAT for the external IP address for legacy.example.com to the Exchange 2003 platform. >>
The request will still have to make it to the CAS server inside the network in order for the CAS to determine if the mailbox is in the Exchange 2003 or not.
At this point if the user mailbox is in 2003, will the request be redirected to Legacy.example.com Internal or External IP address...
Did you get where the confusion is ?
Both internal and external OWA access have to reach CAS server inside the Network to determine if the Mailbox is in 2003 or 2010....if OWA is tried outside and CAS found that the mailbox is in 2003 why CAS would not redirected to the internal IP address of legacy.example.com instead to the external IP??/
Ok, that's when the user is inside the network and trying to use OWA. the legacy.example.com here should be pointing to FE
==========================
<<If external then it will be a query against your external IP address. You just need to ensure that you are pointing the NAT for the external IP address for legacy.example.com to the Exchange 2003 platform. >>
The request will still have to make it to the CAS server inside the network in order for the CAS to determine if the mailbox is in the Exchange 2003 or not.
At this point if the user mailbox is in 2003, will the request be redirected to Legacy.example.com Internal or External IP address...
Did you get where the confusion is ?
Both internal and external OWA access have to reach CAS server inside the Network to determine if the Mailbox is in 2003 or 2010....if OWA is tried outside and CAS found that the mailbox is in 2003 why CAS would not redirected to the internal IP address of legacy.example.com instead to the external IP??/
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks
ASKER
when a user is inside the network and wants to use OWA, they will type https://mail.domain.com, then type user name and password, they reach the CAS sever, which in turns looks for the user mailbox location, if it is in Exchange 2003 , it will redirect the request to legacy.domain.com as specified in the INTERNAL DNS record.
the legacy.domain.com record points to Front End exchange 2003 server...
Correct ??
==========================
if a user is outside the network and wants to use OWA, they will type :
https://mail.domain.com, then type user name and password, the request will be redirected to Public DNS then to the public IP of mail.domain.com, as the protocol is 25 (SMTP) the firewall will redirect the request to the internal IP address of CAS server, which in turns looks for the user mailbox location, IF IT IS IN EXCHANGE 2003, Would the request be redirected to the External IP address of Legacy.domain.com (located in the public DNS record ) OR to the Internal IP address of legacy.domain.com (located in the internal DNS record).??
If it will be redirected to the Internal DNS to resolve legacy.domain.com, it means that the external legacy.domain.com will never be used....
if it will be redirected to the external DNS to resolve legacy.domain.com, it means that it does not make sense, while the request made it all the way to the internal network , then it should make sense to use the internal DNS to resolve the legacy.domain.com... inh stead of being redirected to the external DNS record legacy.domain.com
To my understanding the Legacy.domain.com in the public DNS, is of No Use....
please let me know if my confusion is not understood