VCS DNS Resource

[adnan_baig]

Hi Everyone,

First let me brief you about our scanrio. we have two Site (Primary & DR). we have two node VCS cluster on primary site and single vcs node on DR site. Both sites are using differenet subnet e.g for location-1(Primary) we have 172.16.1.x/24 subnet and for location-2 we have 172.18.4.x/24 subnet. Also we have two seprate DNSs for both sites and their Zone files are replicating.

Now i want to configure a DNS resource in VCS cluser to seamless connectivity for the clients in case of primary site failure. I am confused what exact CNAME record will be added in DNS which will identify the both locations. For example i want to use www alias for both location1(hostname) and location2(hostname).

what entries will be added in DNS servers (we have two DNS servers)?

Thansk,,

[mikebounds · Accepted solution]

For DNS resource on primary site cluster you should have something like:

ResRecord  = { www=pri  }

Domain = "app1.com"

StealthMasters = { "pri_dns_server_ip", "dr_dbs_server_ip" }

and for DR resource on DR cluster, something like:

ResRecord  = { www=dr  }

Domain = "app1.com"

StealthMasters = { "pri_dns_server_ip", "dr_dbs_server_ip" }

You should manually add static entry A-records in DNS something like:

172.16.1.5 pri.app1.com

172.18.4.5 dr.app1.com

When the DNS resources onlines on site 1, if www.app1.com does not resolve to pri.app1.com, it will delete any previous www.app1.com entry and add (to both DNS servers specified by StealthMasters :

attribute)

www.app1.com -> pri.app1.com

and so as pri.app1.com is 172.16.1.5, this means www.app1.com resolves to 172.16.1.5

When you offline DNS resource, nothing happens so if you switch between local nodes at site 1, then nothing will change, but if you online at site 2, then DNS changes to effectively:

www.app1.com -> dr.app1.com -> 172.18.4.5 

Mike

Symantec Consultant in VCS, GCO, SF, VVR, VxAT

If this post has helped you, please vote or mark as solution

[Zahid_Haseeb]

Its an old article but I hope I will help you

http://www.symantec.com/business/support/index?page=content&id=TECH37399&key=15066&actp=LIST

[shahfar]

Hi Adnan,

Does your setup require a DNSupdate agent that creates a new DNS record and deletes the old DNS record on your respective site? Something similar to the setup where you cluster the SQL server for MS share point and where VCS updates the DNS record to the Share point NLB?