Hello all! We are rolling out more and more multi-subnet clusters here at my company and we're running into a pain point with RegisterAllProvidersIP. By default, when we create the AGL, RegisterAllProvidersIP is at 1. This means that the first DNS record that's registered for the AGL name will have both IPs attached to it. After that, we set RegisterAllProvidersIP to 0, but we don't see a DNS record update to remove the offline IP from it. It doesn't appear to be any sort of DNS replication issue, so my question more turns to: "how do we force an update of an AGL's DNS record?" I have tried firing off a Stop-ClusterResource/Start-ClusterResource as well as performing a subnet failover, neither of which seems to work.
Does anyone have some more insight into this? Our end goal is to only have one IP attached to our AGL DNS record as soon as possible after setting it up.
Cheers! Brandon Tucker, Database Developer / DBA, OppenheimerFunds