Solved

DNS Record Change for Exchange Failover

Posted on 2014-01-16
5
501 Views
Last Modified: 2014-01-31
We are looking to configure\fine tune our Exchange 2010 failover scheme. Currently we have a cas array (via a Kemp Load balancer) in production by the name of CAS00. CAS00 is the RPC server for all of our local Outlook clients.

We also have a CAS server in our disaster recovery site by the name of CAS03. We are thinking, when CAS00 in production goes down, we can manually change the DNS A record of CAS00 to point to the IP address of the DR Cas server. This way the clients still point to the CAS00 RPC server but the DR server is actually handling the exchange requests.

I was told something about creating a cname record that points record to tie into the failover scheme which would have a shorter TTL than the A record to create some sort of DNS redundancy and make the process more automated.

Can anybody shed any light as to how to accomplish this?
0
Comment
Question by:GR JN
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 37

Expert Comment

by:Mahesh
ID: 39786876
Yes, you have to change the DNS Record for the CAS Array name in DNS in order to route all connections to the DR CAS Server

Mahesh
0
 

Author Comment

by:GR JN
ID: 39786902
Yes, I know that but is it just the A record or can we tie in a cname record as well?
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39786946
Cname record is not required

You need to point your existing  CAS server \ CAS Array Host(A) record to DR CAS server

http://social.technet.microsoft.com/Forums/exchange/en-US/704695d4-dfb2-40dd-ad58-46b34dc1aa38/exchange-2010-site-resiliency-cas-array-failover?forum=exchange2010

Mahesh
0
 
LVL 5

Accepted Solution

by:
piwowarc earned 500 total points
ID: 39801587
Hello

DNS is not "state aware" load aware mechanism. You can't achieve any failure aware system that would automatically failover to DR server. For that you need actual load balancer.

Active Load Balancing can be achieved with DNS actually. IT is frequent for high traffic and reslient deployments (do nslookup of google for ex). If you give all servers behind this Kemp LB same name, DNS will return addresses to users at random achieving load sharing. It will still be a bit worse that actual LB you have as it will still give IPs of servers that may have gone down.

In general Load Balancers are way better to do any auto failovers than using DNS.

Regards
0
 

Author Comment

by:GR JN
ID: 39824648
wa
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In-place Upgrading Dirsync to Azure AD Connect
This article demonstrates probably the easiest way to configure domain-wide tier isolation within Active Directory. If you do not know tier isolation read https://technet.microsoft.com/en-us/windows-server-docs/security/securing-privileged-access/s…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question