Thursday, October 23, 2008

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name event ID 1196 and Event ID 1119


After setting up windows 2008 Cluster with SQL and Exchange 2007, the following event logs are showing on the event log of the both clusters. The errors are not causing any fail over or operational issues but interesting to investigate and needs resolution

Inside technical info:

Below errors indicating that, the Active cluster node is not able to register the "Cluster name resource" into its own configured DNS server. Basically this is what is happening. The Cluster does have resource called Cluster network name resource. This is one of the resources must be created prior to setting up a cluster and it is being created manually in the DNS database. The cluster active node will own this resource and the active node production network interface will go to its configured DNS and will try to register the cluster name resource record to the DNS database itself. In this example the DNS is refusing the registration, because DNS knows the server does not own the resource name, and hence it is not allowing the active role node to register it.

What does cluster network name resource do?

"The name of the SQL Server is defined by the network name cluster resource, and that name will be used by applications and end users to connect to the failover instance; together these resources represent a logical Windows Server on the network, while running across one or more real Windows Server computers. A failover instance of SQL Server is an item that is created during SQL Server setup; it is not provided by Windows Server."

Root Cause:

When static record got created the option "allow any authenticated user to update DNS records with the same owner" was not selected. Therefore the Cluster nodes (active node) who will own the cluster name resource won't be able to register this resource record to the DNS database behalf of the resource records itself.


Go to DNS, find the record ( A & Pointer record) for the cluster name resource.

  • Make a right click
  • Go to properties
  • In the security make sure the "Authenticated users" are included
  • Make sure it has "Write: rights and Special permissions
  • Click Advance, locate authenticated users, and click edit
  • Make sure, Write all properties, Read permissions, All Validated Writes selected
  • Click okay tree times to exit

After investigating further, you will notice there are no more errors on the System logs in this regard

Log Name: System

Source: Microsoft-Windows-FailoverClustering

Date: 10/23/2008 9:30:35 PM

Event ID: 1196

Task Category: Network Name Resource

Level: Error





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

DNS operation refused.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

Event Xml:

<Event xmlns="">


<Provider Name="Microsoft-Windows-FailoverClustering" Guid="{baf908ea-3421-4ca9-9b84-6689b8c6f85f}" />




<TimeCreated SystemTime="2008-10-24T01:30:35.648Z" />


<Correlation />

<Execution ProcessID="1956" ThreadID="20004" />



<Security UserID="S-1-5-18" />

<Data Name="ResourceName">Cluster Name</Data>

<Data Name="StatusString">DNS operation refused.



Oz ozugurlu

MVP (Exchange)


MCSE (M+,S+) MCDST, Security+, Server +,Project+



Robbie said...

I don't get the 1196 events but I do get the 1119 and adding Authenticated Users to the DNS entries does not fix the 1119 for me. Any other ideas?

Oz Casey Dedeal said...

I am not sure if you delete the A recors and re-created it,

Delete the A record ( No impact for Cluster) re-create it with the option
Allow any authenticated user to update DNS record with the same owner name

if you are still having the same issue please post the errors here

David Caldwell said...

We are geting this same error and need to figure out how would you do this if you are running ISC Bind DNS (version 9.4.3-P3).

The address of the cluster was added to the bind directive "allow updates", so the cluster installation moves further along. But the A record was never actually created by the process and it is unclear if this is a good path to follow.

Any help would be appreciated. Thanks!

Oz Casey Dedeal said...

Deleting the records in DNS and allowing updates is very harmless to be honest, I have done it several times and did not effect to cluster at all. From experience I would say go head create the records you are missing to make the cluster happy and allow the updates


MarcL said...

Thank you, this article solved my Event ID: 1196 problem.

Anonymous said...

Thanks! Worked for us too.

Anonymous said...

Thank much!!!, this article solved my Event ID: 1196 problem too.

sqlservermasters said...

ook me time to read all the comments, but I really enjoyed the article. It proved to be Very helpful to me and I am sure to all the commenters here! Its always nice when you can not only be informed, but also entertained! Im sure you had fun writing this article.
Valuable information and excellent design you got here! I would like to thank you for sharing your thoughts and time into the stuff you post!!

Anonymous said...


Thanks for sharing.

Take a look at this article below:

Does it mean IP address of cluster DNS will not be static anymore?

What is the implication/risk?