Cluster network name resource failed to register in a secure DNS zone because record was already registered and owned

Microsoft.Windows.6.2.Cluster.Cluster.network.name.resource.failed.to.register.in.secure.DNS.zone.because.record.was.already.registered.and.owned (Rule)

Knowledge Base article:

Summary

In a cluster, a Network Name resource can be important because other resources depend on it. A Network Name resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.

Event Details

Event ID:

1576

Source:

Microsoft-Windows-FailoverClustering

Symbolic Name:

RES_NETNAME_DNS_REGISTRATION_SECURE_ZONE_REFUSED

Message: Cluster network name resource '%1' failed to register the name '%2' over adapter '%4' in a secure DNS zone. This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record. The error code was '%3'. Please contact your DNS server administrator to verify the cluster identity has permissions on DNS record '%2'.Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).

Causes

This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record.

Resolutions

Check events related to updating a DNS record

Check your DNS server event log or WINS server event log for further information. If needed, generate a network trace to see what happened during the process of accessing the DNS server or WINS server.

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain."

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Opening Event Viewer and viewing events related to failover clustering

To open Event Viewer and view events related to failover clustering:

Finding more information about the error codes that some event messages contain

To find more information about the error codes that some event messages contain:

NET HELPMSG errorcode

Verify

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Verifying that a Network Name resource can come online

To verify that a Network Name resource can come online:

To perform a quick check on the status of a resource, you can run the following command.

Using a command to check the status of a resource in a failover cluster

To use a command to check the status of a resource in a failover cluster:

CLUSTER RESOURCE ResourceName /STATUS

If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.

Element properties:

TargetMicrosoft.Windows.6.2.Cluster.Monitoring.Service
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Cluster network name resource failed to register in a secure DNS zone because record was already registered and owned
{0}

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.6.2.Cluster.EventProvider Default
WA WriteAction Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription Default

Source Code:

<Rule ID="Microsoft.Windows.6.2.Cluster.Cluster.network.name.resource.failed.to.register.in.secure.DNS.zone.because.record.was.already.registered.and.owned" Enabled="true" Target="Clus8Library!Microsoft.Windows.6.2.Cluster.Monitoring.Service" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.6.2.Cluster.EventProvider">
<Criteria>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>1576</Value>
</ValueExpression>
</SimpleExpression>
</Criteria>
<LogName>System</LogName>
<PublisherName>Microsoft-Windows-FailoverClustering</PublisherName>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WA" TypeID="ClusLibrary!Microsoft.Windows.Cluster.GenerateAlertAction.SuppressedByDescription">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.6.2.Cluster.Cluster.network.name.resource.failed.to.register.in.secure.DNS.zone.because.record.was.already.registered.and.owned.AlertMessage"]$</AlertMessageId>
</WriteAction>
</WriteActions>
</Rule>