大网数据广告活动
故障转移群集

Windows Server 2019 cluster role doesn't come online after you rebuild the cluster

· 52CE 我爱测

Discusses how to resolve an issue in which a Windows Server 2019 cluster role doesn't come online on a specific node after you rebuild the cluster.

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:

  1. Verify that the CNO exists in Active Directory, and that it isn't disabled.
  2. Verify that the CNO has sufficient permissions to update records in the secure DNS zone. Follow these steps:
    1. In the DNS Manager console, locate the forward lookup zone for your cluster domain.
    2. Right-click the zone, select Properties, and then select Security.
    3. Verify that the CNO has the Create all child objects and Write all properties permissions.
    4. If the permissions are missing, configure them.
  3. Try to bring the cluster role online.
  4. To test the cluster, perform a manual failover.
  5. 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.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/27/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。