Active Passive DAG seperate DNS namespace

Not open for further replies.


Hello all

I have read many Microsoft KB articles on the requiremnet for having a dual namespace, when a DAG stretches across 2 or more AD sites. If i am running in an Active\Passive DAG design and the datacenter that contains the passive copies is for DR purposes only, then i dont see the requirement for having a seperate namespace for the DR site, because in the event of a failover to the DR site, all i need to do is update the ip address for the following below DNS records, (internal and external DNS) and point these records to the WNLB vip in the DR site, we will use split DNS. Again in the event of a datacenter swithcover, if i can move the DNS records so they point to the WNLB vip thats located in the DR site, then i dont understand the need for a seperate DNS namespace for the DR site? Again the DR site will be used for DR purposes only. I think per my settings having to have a seperate DNS namespace just over complicates the environment. (internal and external DNS) (external DNS) (casarray, internal DNS)

Bulls on Parade

Brian Day MCITP

Do you have a plan in place to deal with partial datacenter switchovers? What I mean by that is what if only one or two datbases have to be activated in the secondary datacenter and not all of hem?Microsoft Premier Field Engineer, Exchange
MCSA 2000/2003, CCNA
MCITP: Enterprise Messaging Administrator 2010
Former Microsoft MVP, Exchange Server
My posts are provided "AS IS" with no guarantees, no warranties, and they confer no rights.


I cant think of any reason why i would need to activate one or two databases in the DR datacenter. I will have 4 mailbox servers in a single DAG stretched across two AD sites. the FSW wintess will be located in the primary DC. With this configuration i could lose two servers and still maintain quorum. The mailbox servers have been sized and speced out to acomodate 100% of the databases in the event one of the mailbox servers went down. If i am udnerstanding you correctly it sounds like per my setup, i would only need a seperate namespace if i wanted to plan for a partial datacenter switchover where one of two databases become active in the DR site? I can understand needing a seperate namespace to suppor this, but this is not in our plan.

Bulls on Parade

Brian Day MCITP

I cant think of any reason why i would need to activate one or two databases in the DR datacenter. I will have 4 mailbox servers in a single DAG stretched across two AD sites.

Do you have 4 copies of each DB? If so, let's say you have copies 1/2 in Site-A and copies 3/4 in Site-B

Playing devil's advocate here...

Perhaps the content index becomes corrupt on copy 2 and Murphy's Law kicks in and at the same time copy 1 suffers from something else which causes it to dismount. You now have to rely on copy 3 or 4 to mount while you repair copies 1/2. Depending on DB and CI size, and WAN speed between sites this could take a while.

Microsoft Premier Field Engineer, Exchange
MCSA 2000/2003, CCNA
MCITP: Enterprise Messaging Administrator 2010
Former Microsoft MVP, Exchange Server
My posts are provided "AS IS" with no guarantees, no warranties, and they confer no rights.


It shouldt take a while to mount, the 3/4 copies in the DR site, should be pretty much up to date with log file replication. In the event i have to activate copies 3/4, the users who now access there mailbox in the DR site, would still use the primary sites CAS servers for internal and exeternal access and these CAS servers will proxy the connection to the CAS servers in the DR site that contain the 3/4 active database copies in the DR site. As long as the internalurl for the EAS, OAB, OWA and EWS virtual directories are configured and the external url is null, then proxying will work, so again i really dont see the need for a seperate namespace for the DR site? With Exchange 2010 sp1 the CAS servers can do cross site connections, for outlook 2010 across datacenters to the mailbox sever that now has the 3/4 database active. Basically the outlook 2010 client will connect to the CASarray in the primary DC, at this time the CAS array located in the primary DC will do a direct connect to the mailbox server located in the DR site. This is the default behavior in SP1

What i am still having a hard time understanding is, if i will be using WNLB in both datacenters, and in order for proxying to work for OWA, and ECP the internalurl property for these virtual directories must be set to the the FQDN name of the server, if this is true and i have 2 cas servers configured in a WNLB array, then how can i load balance this type of traffic? The CAS servers in the primary site, will proxy the connection to the value configured for the internalurl for the CAS servers in the DR site, if i have more than 1 CAS server, then what CAS server should i use?

Bulls on Parade

Brian Day MCITP

Mounting 3/4 will (hopefully) be almost instantaneous. I was trying to point out out it may take a while to reseed the content index or EDB in Site-A if something like that were to happen and without dedicated namspaces it can make datacenter switchovers move involved as the steps to switchover can be more. It also depends a lot on what version of clients you're using.

If you're comfortable with utilizing proxying (don't forget to enable WIA on the vDirs as well) then you can run in that configuration. It isn't optimal from a performance point of view (RPC over the WAN is more costly and latency depdendent than HTTPS over the Internet), but if you are willing to accept it for partial datacenter activations then there's nothing inherently wrong with it. You'll have to back out the proxying config to a normal config during a full datacenter switchover scenario, so make sure those are part of the switchover documentation.

In SP1 the cross-datacenter RPC connections feature you're thinking of didn't make the SP1 RTM cut. It was unfortunately removed from SP1 before the bits were release to the world, but it hasn't yet been removed from the documentation. Hopefully it comes back later, but there is no way to prevent cross-datacenter RPC connections at this time short of activation blocking DB copies in the remote datacenter.

Yes, FQDNs for proxy sites is one of the drawbacks to proxying and where dedicated namespaces would be more valuable as we could simply redirect the user to the more approprate ExternalURL value. Without a FQDN on the InternalURL value for a proxy situation we wouldn't be able to utilize Kereros and authenticate between the CAS servers. You have to rely on Exchange itself not always choosing the same CAS server when it does a lookup, but that isn't guaranteed not to happen.
Microsoft Premier Field Engineer, Exchange
MCSA 2000/2003, CCNA
MCITP: Enterprise Messaging Administrator 2010
Former Microsoft MVP, Exchange Server
My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.


Makes sense, and thank you for the help and information. I must confess this topic of needing two separate DNS namespaces, when a DAG is stretched across separate AD sites is a bit convoluted and confusing. The main point to consider with this is knowing understanding and preparing for a datacenter switch over and or a database switch over. With an active\passive DAG that spans two AD sites, the main reason or purpose for the separate namespace for the DR site when a database switch over occurs, is to be able to support OWA, and EAS clients as the externalurl value for these virtual directories would be configured with the DR sites namespace i.e This DNS record would be in external DNS and internal DNS. Outlook 2010 clients that are configured for outlook anywhere would also use these values in order to find the exchange web services. Basically they would perform an autodiscover lookup the DNS record for this in external DNS is still pointing to the CAS servers located in the primary AD site. Because there mailbox is now in the DR site, the Outlook anywere clients will receive new connection settings per the DR site ( and connect.

When a datacenter switch over occurs, the external DNS records for and need to move to the DR datacenter. EAS, OWA and outlook anywhere now connect to the DR Datacenter, and because all the url's in the DR datacenter have been configured with the namespace, these clients continue to connect without issue. A few things need to be done to support this configuration

#1 configure one SAN cert.

Principal name =

Subject alternative names =,, this cert gets imported to all CAS servers across the org

#2 Configure the outlook provider on all CAS servers across the org, so it points to

This design assumes the following configuration

1Pure Ecxhange 2010 org

2consists of two DC both with internet connectivity

3No proxy sites

4uses split DNS

5an AD site in each Datacenter

6the DAG includes member servers from each datacenter

7WNLB or HLB is used is deployed each DC

8SAN certs are used

Bulls on Parade
Not open for further replies.
Thread starter Similar threads Forum Replies Date
B DAG with active passive database configuration Exchange Server Administration 13
M DAG Active Passive on seperate LUNS Exchange Server Administration 5
N Identify if the database in Exchange 2010 DAG is active/passive Exchange Server Administration 3
C active/passive broadband connections to maintain various IT services Exchange Server Administration 2
E Active and Passive database copies on same server Exchange Server Administration 1
P Active/Passive Cluster move from Local attached storage to iSCSI Exchange Server Administration 8
P Automate Outlook Start - No Active Explorer Object Found Using Outlook 10
S Active Directory Management Tools for Administrators New Articles 0
G Problems with Active Directory Rights Management Services (AD RMS) in Outlook 2013 Exchange Server Administration 0
Diane Poremsky Import Images into the Active Directory New Articles 0
S How to send an OUTLOOK task to a contact out of my active directory? Using Outlook 2
E Outlook rule only active certain times of day Using Outlook 6
R HELP!!! Email template with active excel spreadsheet Using Outlook 1
R Went from outlook 2003 to 2010 - can't retrieve active for contacts Using Outlook 0
J Setup mail for Exchange 2010 through Active Directory on Server 2008 R2 Standard Exchange Server Administration 3
W active sync Using Outlook 2
T Copied Contact Does Not Update With Active Directory Information Changes Immediately. How Do I Force Update? Using Outlook 1
E Using with Active Sync, Outlook become unresponsive Using Outlook 5
B Re: Exchange OOF / EWS Problem - The user and the mailbox are in different Active Directory sites Exchange Server Administration 0
M 'Send link by E-mail' doesn't provide active link.__ Using Outlook 1
J When a database move from active host in a DAG, user are prompted for credentials Exchange Server Administration 8
D Using Inbox as 'Active' tray, with both incoming and 'sent' mail, with senders and receivers displayed. Using Outlook 1
U Outlook 2010 Ignore Conversation Feature, list of Active Ignored Using Outlook 1
D how to give perrmission on calender to user in ACTIVE DIRECTORY Using Outlook 0
J OWA not working when active database moved Exchange Server Administration 3
S Web Links are not active when using Outlook Web Access 2007 Using Outlook 1
P How can I convert an Outlook 2010 folder to a .pdf with active links like I could in Outlook 2007? Using Outlook 3
T The Microsoft Exchange Active Directory Topology service on server localhost can't be contacted via Exchange Server Administration 2
P Will 'ldap modify' command work on some Active Directory fields? Using Outlook 2
B Active Active Site Resilience Exchange Server Administration 3
E Event ID 9514 - Two objects in Active Directory have the same proxy address Exchange Server Administration 3
K publish exchange active sync behind TMG Exchange Server Administration 4
S Active Sync Device ID Using Outlook 2
C Active Directory error applying Exchange 2010 SP1 Exchange Server Administration 4
E Transfer calendar from a .pst to a user's active exchange account? Using Outlook 7
M Active Manager operation failed to mount DB Error Id: 50A399C7, ErrorId: BF128831 Exchange Server Administration 10
P Ex2010 active sync Exchange Server Administration 4
R Hi, Is Outlook 2010 compatible thru active sync with Windows Mobile 6.1 Professional. Using Outlook 4
O Exchange 2010 Service Pack 1 Active Directory Schema Exchange Server Administration 1
F Active Sync proxying not works in a Exchange 2010/2007 Coexistence Exchange Server Administration 1
K An Active Manager operation fail Exchange Server Administration 6
A No Word e Outlook 2010 não funciona o rolamento de página (scroll active) com mouse. Como corrigir Using Outlook 1
T Active Directory domain 'FECR' has an unrecognized Exchange signature. Current DomainPrep version: 1 Exchange Server Administration 2
M DAG Active/Active Exchange Server Administration 2
S Exchange 2010 - Active Sync issue - Samsung Galaxy S Exchange Server Administration 2
A CAS Proxying with Active Sync when migrate from Exchange 2007 to 2010 Exchange Server Administration 1
S Outlook reply window default tabs have changed from message being active, to now File being active. Using Outlook 1
P Send button is missing and account is active, can receive but can not send. Email removed for priva Using Outlook 1
V Restoring calender files that were deleted by Active sync Using Outlook 1
M Exchange 2010 Active Sync Device Recovery Password is not VISIBLE in OWA Exchange Server Administration 4
Similar threads