Summary
Use this article to resolve a Windows Server 2019 failover cluster issue in which a cluster role doesn't come online on a specific node after you rebuild the cluster. Typically, this issue indicates that the Cluster Name Object (CNO) doesn't have the correct permissions to update the secure Domain Name System (DNS) zone. This article explains the symptoms, root cause, and recommended resolution steps.
Symptoms
You rebuild a Windows Server 2019 failover cluster, and then you encounter one or more of the following symptoms:
-
On one particular node, cluster roles don't run.
-
On that node, the event log displays the following error message that indicates a permissions issue:
Cluster network name resource failed registration of one or more associated DNS name(s) because the access to update the secure DNS was denied. -
A generic role doesn't fail over to another node. In fact, unless you involve your cluster vendor, no roles fail over successfully.
The issue persists even if you destroy the cluster and then rebuild it.
Cause
This issue occurs if the cluster network name resource can't register its DNS names because the CNO doesn't have the required permissions to update the secure DNS zone. Without these permissions, DNS registration fails. Therefore, the cluster role on the affected node can't come online.
Resolution
To resolve this issue in Windows Server 2019 failover clusters:
- Verify that the CNO exists in Active Directory, and that it isn't disabled.
- Verify that the CNO has sufficient permissions to update records in the secure DNS zone. Follow these steps:
- In the DNS Manager console, locate the forward lookup zone for your cluster domain.
- Right-click the zone, select Properties, and then select Security.
- Verify that the CNO has the Create all child objects and Write all properties permissions.
- If the permissions are missing, configure them.
- Try to bring the cluster role online.
- To test the cluster, perform a manual failover.
- Review the event logs to verify that DNS registration succeeds and doesn't generate permission errors.
After you grant the correct permissions to the CNO, failover between nodes should work as expected.
Data collection
If the issue persists after you finish the resolution steps, collect the following data, and then contact Microsoft Support:
-
Cluster logs from all nodes. To collect logs, run the following command on one of the cluster nodes:
Get-ClusterLog -UseLocalTime -Destination <folder path></folder> -
Relevant event logs from FailoverClustering and DNS Server event log channels.
-
Details of the CNO object in Active Directory, including security permissions.
This information helps support engineers quickly identify permission or configuration issues.
References
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: kaushika-msft). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
