This was not an issue with Windows 2008 Clustering but was instead an oversight when windows clustering was configured. For clustering, the Cluster resource name must have full access to the Virtual Cluster Names, so when failover takes place, DNS entries can be updated.
Following errors were recorded in event logs when it registrations fail:
Cluster network name resource ‘SQL Network Name (VirutalClusterName)’ failed registration of one or more associated DNS name(s) for the following reason:
DNS signature failed to verify.Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
To fix this, you’ll need permissions to update the DNS entire permissions for the VirtualClusterName resource name:
- In DNS Management (dnsmgmt.msc):
- Find the VirtualClusterName that is failing to register.
- Right-Click Properties.
- Select the Security Tab.
- Click Add.
- Click Object Types.
- Check off “Computers“; uncheck other options selected.
- Enter in the name of the cluster (a.k.a Cluster Name Object (CNO)).
- Click Check Names; Verify that the entry has been found.
- Click OK.
- Give the CNO FULL Control over this record.
- Click OK.
SQL Canada (SQLCAN) 
Thank you. Good trick.
Your welcome, I am glad information on the blog helps someone :).
Thank you. I actually found this while looking for the solution to another problem. But it helped me solve another problem of adding a second SQL instance to a cluster. Been looking for that answer to two weeks now. Thanks.
Dear sir your reply is much appreciated i build Windows Cluster on Windows Server 2012 R2 in VM environment then i build SQL Server Cluster in the first node everything is ruining fine but at the end the SQL Cluster Services can not bring online when i checked the Event Viewer i found lot of errors one of the error you mention it on your post and the below error Also so can you advice me about if it is my case related to your post or now before i will send this recommendation to the system team to do fix the issue :
Event Error
Cluster network name resource ‘SQL Network Name (HQDB-TS-CLS-02)’ 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.
DCOM was unable to communicate with the computer HQDB-TS-CLS-02 using any of the configured protocols; requested by PID 1170 (C:\Windows\system32\ServerManager.exe).
Clustered role ‘DEVSQLGroup1’ has exceeded its failover threshold. It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
The Cluster service failed to bring clustered role ‘DEVSQLGroup1’ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.
Cluster resource ‘SQL Server (SQLDEV)’ of type ‘SQL Server’ in clustered role ‘DEVSQLGroup1’ failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Your help is much appreciated
Mustafa EL-Masry
Principal Database Administrator & DB Analyst
SQL Server MCSE, MCSA, MCITP, MCTS
http://mostafaelmasry.com/
DBConsultant@MostafaElmasry.com ; SQLGULF@MOstafaElmasry.com
thanks
You have multiple issues here.
1) DNS operation refused. Most likely cause is CNO (Cluster Name Object) does not have permissions to update the DNS entries.
2) DCOM was unable to communicate. I suspect firewall issues.
3) Failover threshold; by default windows allows 1 automatic failover for every 6 hours. After which it will refuse to failover. Confirm that Failback settings are turned off.
Rest of the messsages are normal.