We worked with Microsoft extensively throughout the Server 2012 TAP program providing feedback in various areas. We encountered an issue late in the program when creating a Server 2012 cluster on our production domain. We did not see this same issue in any lab environment, or in our development environment which mirrors production.
When attempting to create the cluster, the wizard would fail when creating the AD objects. We confirmed that the user had proper permissions, and did not encounter the same issues creating 2008 or 2008 R2 clusters on our production domain. After working with Microsoft, they recommended we install KB 976424 on our production domain controllers. After installing this hotfix and rebooting all of the domain controllers, we were able to create a Server 2012 cluster on our 2008 domain without issue.
I have a similar issue. I work for a software company and we’re testing our product on 2012. In my test environment I have a 2008 R2 AD domain. I have a 3 node 2012 cluster and I’ve noticed my resources don’t register in DNS. I also see this,
“Cluster network name resource ‘Cluster Name’ failed registration of one or more associated DNS name(s) for the following reason:
DNS server failure.”
I don’t have this problem with a 2008 cluster…any advice?
Doesn’t sound like the same issue here. From what I can tell, your issue looks to be related to DNS. Make sure DNS is configured properly for the cluster nodes and that the user account creating the cluster has permission to update the DNS records.
It was a DNS issue in which I had to add a 2012 DNS server to my 2008 AD environment. Why? Million dollar question, but until I added that 2012 DNS server into the mix, I had problems.