Failover Cluster DNS Record For vIP Is Scavenged

Copper Contributor

I have a physical, two node Windows 2016 failover cluster that is periodically unable to refresh the DNS entry for its virtual IP. There is no rhyme or reason and the only way to remedy the issue is to delete the record and reboot the cluster nodes one at a time.

I have been through all of the troubleshooting articles RE: AD permissions and the issue persists. At this point I am done troubleshooting and would like to just create the DNS record statically, is there any reason I should not do this? 



0 Replies