Cluster network name resource failed to register dynamic updates for DNS name

Summary

In a cluster, a Network Name resource can be important because other resources depend on it. A Network Name resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.

Event Details

Causes

The Request for Comments (RFC) 2136 allows for a dynamic update response to be formed by using the following two methods:

• 1.Respond by using the ZOCOUNT, PRCOUNT, UPCOUNT and ADCOUNT fields copied

• 2.Respond by using the ZOCOUNT, PRCOUNT, UPCOUNT and ADCOUNT fields set to 0.

The DNS server on a computer that is running Windows Server 2008 R2 uses method 1, while the third-party DNS servers use method 2.

This problem occurs because of the way a computer that is running Windows Server 2008 R2 interprets the response packet received from a DNS server. This interpretation occurs after you try to dynamically register SRV records.

A DNS client that is running Windows Server 2008 R2 treats a response that uses method 2 as a bad packet, even though the returned status code for the update is "success." This behavior causes the NETLOGON Error event ID 5774 that has a status code of 9502 (DNS_ERROR_BAD_PACKET) to be logged or blocks the cluster from bringing resources online in scenario 2.

Resolutions

Check DNS configuration

The Network Name resource could not register one or more Domain Name System (DNS) names. If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain." After reviewing event messages, check the following:

• Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.

• Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.

• Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Opening Event Viewer and viewing events related to failover clustering

To open Event Viewer and view events related to failover clustering:

• If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

• In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.

• To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.

• To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.

Finding more information about the error codes that some event messages contain

To find more information about the error codes that some event messages contain:

• View the event, and note the error code.

• Look up more information about the error code in one of two ways:

• Search System Error Codes ( http://go.microsoft.com/fwlink/?LinkId=83027).

• Click Start, point to All Programs, click Accessories, click Command Prompt, and then type:

NET HELPMSG errorcode

Verify

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Verifying that a Network Name resource can come online

To verify that a Network Name resource can come online:

• To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

• In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.

• If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.

• In the console tree, click a clustered service or application.

• In the center pane, view the status of the Network Name resource you want to verify.

• If a Network Name resource is offline, to bring it online, in the center pane, right-click the resource and then click Bring this resource online.

To perform a quick check on the status of a resource, you can run the following command.

Using a command to check the status of a resource in a failover cluster

To use a command to check the status of a resource in a failover cluster:

• On a node in the cluster, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

• Type:

CLUSTER RESOURCE ResourceName /STATUS

If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.