Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
The handle is invalid.
.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
There are many posts on the internet addressing this problem but none of them worked for us. take a look at them if you want:
- http://smtp25.blogspot.nl/2008/10/cluster-network-name-resource-name_23.html
- http://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/
- http://haythamalex.wordpress.com/2012/10/02/cluster-name-failed-registration-of-one-or-more-associated-dns-names-for-the-following-reason/
- http://jaminquimby.com/joomla253/9-uncategorised/473-cluster-name-resource-failed-registeration-in-dns
All posts point to DNS registration, all fixes do not really touch DNS records.
I our case the DNS record in DNS (the CNO (Cluster Name Object)) A-record turned out to be faulty. when we removed the record we cleaned up our AD-integrated DNS records like this:
- removed A record from the DNS server on which the cluster nodes try to register themselves
- Update Server Data Files
- Clear Cache
- Restart DNS service
- Do this on all DNS servers in your domain or wait for the DNS replication to distribute these changes
- Temporarily move the CNO account into the Computers container
- Log into one of the cluster nodes with a domain account that has the ResetPassword right in the domain
- Simulate failures for the cluster Network Name resource until it is in a permanent failed state
- Once the resource is in a Failed state, right-click on the resource, choose More Actions and then click Repair
Important information on Error 1196: Microsoft has provided a Hotfix alailable for download here:
http://support.microsoft.com/kb/2838043
No comments:
Post a Comment