"DNS bad key" on Windows Failover Cluster

I used to see two common errors on the new created Microsoft Failover Cluster. "DNS bad key" and CNO update error.

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s):

DNS bad key


Cluster network name resource failed registration of one or more associated DNS names(s) because the access to update the secure DNS Zone was denied.

The error "DNS bad key" is more often rather than the other error. I did a lot of study on the internet. The issue was fixed after applying the following steps:

  1. Right click the Windows button - Click Run.
  2. Run following command to enter Network Connections.
  3. Go to Properties of the network adapter that you are using for Microsoft Failover Cluster.
  4. Go to Internet Protocol Version 4 (TCP/IPv4) - Advanced - DNS tab.
  5. Deselect the Register this connection's addresses in DNS.

Screenshot of the key option to fix the issue.

The cluster error events appears in event log in regular frequency. If you want to test it without waiting. You can initiate a core cluster resource failover to test it.

How to move core cluster resource?

Microsoft Cluster Failover - Right click the cluster - More actions - Move Core Cluster Resources.

Popular posts from this blog

Moving to Blogger.com

How to Use Proxy on WSL 2

Connect-NsxtServer shows "Unable to connect to the remote server"