This error was encountered during a regular failover testing for one of the SQL Server 2008 clustered instance. It won’t failover since SQL Network Name resource fails to come online. From Event logs:
Log Name: SystemSource: Microsoft-Windows-FailoverClusteringDate: 10/6/2012 4:18:26 AMEvent ID: 1196Task Category: Network Name ResourceLevel: ErrorKeywords:User: SYSTEMComputer: Server_NameDescription:Cluster network name resource 'SQL Network Name (SQLVS)' failed registration of one or more associated DNS name(s) for the following reason:DNS signature failed to verify.
I found a blog post on the related error but that didn’t do the trick. I had correct permissions set for the VCO/CNO to update DNS record entries. Upon some further troubleshooting, it turned out that there was a duplicate entry for DNS A-record for the SQAL Network Name in question. To see the DNS record, go to a command prompt and type ipconfig /displaydns and then look for the records of SQL Network name shown in the error above (i.e. SQLVS in this case)
C:\>ipconfig /displaydnswubuatdb03a----------------------------------------Record Name . . . . . : SQLVS.fully.qualified.domain.comRecord Type . . . . . : 1Time To Live . . . . : 830Data Length . . . . . : 4Section . . . . . . . : AnswerA (Host) Record . . . : 18.104.22.168Record Name . . . . . : SQLVS.fully.qualified.domain.comRecord Type . . . . . : 1Time To Live . . . . : 830Data Length . . . . . : 4Section . . . . . . . : AnswerA (Host) Record . . . : 22.214.171.124
As you see, there are two DNS A-records for this SQL Network Name. The second one is problematic since I couldn’t ping that. Further step was to consult our Windows team who confirmed that the latter one is an incorrect entry and seems to have been a left over. To resolve this, delete the problematic DNS record. Alternatively, both the records can be deleted and re-created by ipconfig /registerdns on all the nodes of the cluster.