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.
However if you used a underscore _ a big NO! NO! with NetBIOS and DNS names. Solution: wipe and start over.
If you used a dash -, an exceptable NetBIOS name, your still screwed and got this error. BUG in Windows 2008 R2. You can add the name manualy to the DNS, but it will not be automatic.
Following errors were recorded in event logs when it registrations fails:
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
In DNS Management (dnsmgmt.msc):
However if you used a underscore _ a big NO! NO! with NetBIOS and DNS names. Solution: wipe and start over.
If you used a dash -, an exceptable NetBIOS name, your still screwed and got this error. BUG in Windows 2008 R2. You can add the name manualy to the DNS, but it will not be automatic.
Following errors were recorded in event logs when it registrations fails:
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
In DNS Management (dnsmgmt.msc):
- Find the VirtualClusterName that is failing to register.
- Right-Click Properties.
- Select 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.
No comments:
Post a Comment