Forum Discussion

PlumpJack's avatar
PlumpJack
Copper Contributor
Sep 08, 2020

Bound to unbound namespace

We currently have exchange 2010 spread across 2 datacenters using a bound namespace. Users in the west use the mail-west.domain.com namespace while the users in the east use mail-east.domain.com.  We...
2010
2016
Exchange Server
VickVega's avatar
VickVega
Brass Contributor
Sep 08, 2020

PlumpJack 
Adjusting those FQDNs, basically changes the end-point to which client is connecting for the provided services. Adding mail.domain.com onto the new Exchange 2016 certificate would allow you to point the users to the required client access server, usually the latest Exchange version.  Depends on the state of the other virtual directories on other servers, Exchange accepting the connection would either proxy or redirect.
That's your name space change :).

PlumpJack's avatar
PlumpJack
Copper Contributor
Sep 08, 2020

VickVega  So it is not necessary to update the remaining URLs (ECP,EWS,ActiveSync,OAB) on 2010, to the new namespace?  Won't 2016 proxy the autodiscover request to the server housing the 2010 mailboxes, so 2010 would return the old URLs to the client?  If that is the case, should the old URLs resolve to the exiting vip load balancing the 2010 servers, or the new 2016 vip?

  • VickVega's avatar
    VickVega
    Brass Contributor
    Sep 08, 2020

    PlumpJack 

    All URLs during co-existence would point to 2016 end-point/s, this was way all the traffic would be proxied through to backend 2010.

Resources