When a cluster network name resource comes online, it registers with a DNS server if the DNS server supports dynamic registrations. Any A-Record or AAAA-Record that is registered includes the following information:
- The IP address information for the IP address resource that successfully comes online
- A default Time to Live (TTL) entry
The default private property settings for cluster network name resources may cause delays when clients try to re-connect to cluster resources after a failover of a highly available application or a service group. There are network name resource private properties that can be modified to optimize name resolution behavior. Such optimization makes clients re-connect faster after a failover. The following is a list of the default settings for the private properties that may help in this scenario.
|HostRecordTTL||1200 (0x4b0) seconds|
This is the time during which clients cache DNS record information. The default is 20 minutes.
This setting determines whether all IP addresses on which a network name resource depends are registered in DNS or whether only the IP address resource(s) that successfully come online are registered in DNS. The default setting is to register only those IP address resources that come online.
Note This setting cannot be used in Microsoft Exchange Server 2007 clusters. It will adversely impact MAPI functionality.
For more information about DNS and dynamic updates, visit the following Microsoft Web page:
Article ID: 947048 - Last Review: Sep 11, 2010 - Revision: 1