Public Access URL/DNS with DAG at 2 Sites

Good Day!

I have inherited a DAG environment that doesn't seem to have been configured correctly. There are 3 servers; ex1, ex2, ex3. There are 2 sites; site1 and site2. ex1 and ex2 are at site1, and ex3 is at site2. 

Currently, DNS has an A record that points to ex1. This does no good obviously if ex1 goes down. Ultimately, what I would like, is some kind of Dynamic method to have say exchange.domain.com have a weight or priority, between these 3 servers. I have read a little about the original configuration of a DAG, but I am unsure of how to make the necessary changes to accommodate the DAG and the necessary DNS changes.

Does anyone have any experience with this situation? 

Thank you!

September 8th, 2015 4:47pm

Hi,

This seems to be a question rather than a General Discussion. Remove\Move this and place it in the correct section.

Secondly you are mixing up Ex2010 with Ex2013. What you are talking applies to CAS services only, not the DAG.

Namespace Planning in Exchange 2013:

http://blogs.technet.com/b/exchange/archive/2014/02/28/namespace-planning-in-exchange-2013.aspx

Unlike Exchange 2010, Exchange 2013 does not require the client namespaces to move with the DAG during an activation event a CAS2013 in one Active Directory site can proxy a session to a Mailbox server that is located in another Active Directory site. This means that unique namespaces are no longer required for each datacenter (mail.contoso.com and mail2.contoso.com); instead, only a single namespace is needed for the datacenter pair mail.contoso.com. This also means failback namespaces are also not required during DAG activation scenarios, so mailpri.contoso.com and mailsec.contoso.com are removed.

Free Windows Admin Tool Kit Click here and download it now
September 8th, 2015 11:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics