Answered by:
Cluster-Aware Updating DNS configuration

Question
-
Hello,
I've got a simple 2 node Server 2012 cluster and have configured CAU. It actually runs the updates just fine, but something is not quite right.
When I run Server Manager, it lists the "entity" (I don't know what to call this thing - it's not a server, but it's listed here) that was created when I enabled CAU with the name CAUhvcluxc4 with an error of "Target name resolution error." I tried adding a CNAME DNS entry for CAUhvcluxc4 to point to the name of my cluster, and that caused the error to go away, but it started generating errors in the FCM saying "dns rr set that ought not exist does exist."
I'm sure there's something simple I'm doing wrong here, but I can't figure it out.
Answers
-
Use the Update-ClusterNetworkNameResource PowerShell cmdlet to regsiter with DNS. So in your case it would be -
Get-ClusterResource 'CAUhvcluxc4' | Update-ClusterNetworkNameResource
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
- Marked as answer by Lawrence,Moderator Monday, February 25, 2013 2:52 AM
-
Should be able do, just keep in mind there will be multiple entries equating to the # of nodes in the cluster and the IP addresses will be the cluster node IP addresses.
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
- Marked as answer by JakesterPDX Monday, February 25, 2013 4:51 PM
-
Cool.
I manually populated them, but, yes I think they're correct now.
- Marked as answer by Lawrence,Moderator Monday, February 25, 2013 2:52 AM
All replies
-
If the CAU role is HA in the cluster (the resources cannot be seen in Failover Cluster Manager but only by using PowerShell), CAU role uses a Distributed Network Name resource which will register the CAU Name (CAUhvcluxc4) in DNS. There should be two A-Records each with the IP address of one of the nodes in the cluster)
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
-
-
Hi,
This is a known issue in Windows Server 2012.
Issue:
After you create a failover cluster or configure high availability for a role in Failover Cluster Manager (for example the File Server role), you notice the following:
- The new server name of the failover cluster or the high availability role does not immediately appear in Server Manager when you click File and Storage Services, and then click Servers. If you right-click one of the cluster nodes, and then click Add other servers in the cluster to the server pool, nothing appears to happen.
- If you then click All Servers in Server Manager, the new server name of the cluster or the high availability role is listed. However, the Manageability column displays a status of Target name resolution error.
Cause:
This behavior occurs because of delays that are associated with Domain Name System (DNS) replication. For the new object to appear on the Servers page in File and Storage Services, Server Manager must complete a successful inventory. To do this, Server Manager must wait for the new server name to register and resolve in DNS. Depending on the size of your environment, this can take some time.
Resolution:
Wait until DNS replication completes and the status in the Manageability column on the All Servers page changes to Online. When Server Manager can successfully resolve the server name, the name of the cluster or of the high availability role will automatically appear in the Servers page of File and Storage Services.Tip Server Manager completes an inventory pass every 10 minutes. If you can successfully ping the DNS name of the cluster or the high availability role, you can click Refresh to force an immediate inventory.
For more information please refer to following MS articles:
Known Issues: Windows Server 2012 Failover Clustering
http://social.technet.microsoft.com/wiki/contents/articles/13590.known-issues-windows-server-2012-failover-clustering.aspxHope this helps!
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Lawrence
TechNet Community Support
-
Can you confirm that you made the CAU Role highly available and that you see the resoruces in the cluster by running the Get-ClusterResource PowerShell cmdlet?
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
-
-
Exactly, and that is what you are supposed to get. You will note that one of the resource types is a new one in WS 2012 and that is a Distributed Netwrok Name. This is the same resource that is used with Scale-Out File servers. Then I inspect my DNS Forward Lookup zone and I see two A-Records with the name of the CAU Role (in your example it would be CAUhvcluxc4) and each record has the IP address of one of the nodes in the cluster.
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
-
-
Use the Update-ClusterNetworkNameResource PowerShell cmdlet to regsiter with DNS. So in your case it would be -
Get-ClusterResource 'CAUhvcluxc4' | Update-ClusterNetworkNameResource
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
- Marked as answer by Lawrence,Moderator Monday, February 25, 2013 2:52 AM
-
-
-
-
Should be able do, just keep in mind there will be multiple entries equating to the # of nodes in the cluster and the IP addresses will be the cluster node IP addresses.
Chuck Timon Senior, Support Escalation Engineer (SEE) Windows 8 Beta Engineer Microsoft Corporation
- Marked as answer by JakesterPDX Monday, February 25, 2013 4:51 PM
-
-
-
-
When I went to grab a screenshot of the security error I reported yesterday, the error was gone. Here's how it looks now:
Is it ok that CAUhvcluxc4 is only pointing to one of my nodes at the moment? I've got A Name records pointing to each of my 2 nodes, so maybe it just picks one?
-
-
Cool.
I manually populated them, but, yes I think they're correct now.
- Marked as answer by Lawrence,Moderator Monday, February 25, 2013 2:52 AM