We have an issue with our CSS's that I would appreciate some help with if possible.
We have two CSS's configured, one in each site - with an app session between the two.
We have configured services and contents for an application in each site, which work with no problems.
In addition to the application balancing locally at each site we also have implemented DNS records on both CSS's to try and allow site based failover in the case of a problem:
On CSS designated at "Primary" site:
dns-record a mhs0-x09001.mhs.cfh.nhs.uk 126.96.36.199 5 single kal-icmp 10.149.131.143 2 sticky-disabled weightedrr 10
On CSS designated at "Backup" site:
dns-record a mhs0-x09001.mhs.cfh.nhs.uk 10.149.113.142 5 single kal-icmp 10.149.113.142 2 sticky-disabled weightedrr 0
If we run a nslookup pointed at the primary CSS we always get a response of 188.8.131.52, which is what we want, however if we run a nslookup pointed at the backup CSS we get the following pattern:
10 * 184.108.40.206
1 * 10.149.113.142
Which loops repeatedly.
Does anyone have any ideas? I was of the understanding that specifying a weightedrr of 0 would mean the record would be used unless connectivity to the other site was lost?