Article ID: 252764
Article Last Modified on 2/28/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
This article was previously published under Q252764
SYMPTOMS
Network traces or examination of the cluster log may indicate additional DNS traffic.
The following is an excerpt from the cluster log of a server experiencing this particular issue:
000005d4.00000610::2000/01/28-15:33:48.976 Network Name <Cluster Name>: DNS records for MYCLUSTER have changed. Attempting to reregister.
000005d4.00000610::2000/01/28-15:33:48.992 Network Name <Cluster Name>: Registered DNS name mycluster.reskit.com on IP Address 172.16.12.20.
000005d4.00000610::2000/01/28-15:33:48.992 Network Name <Cluster Name>: Registered DNS name mycluster.reskit.com on IP Address 172.16.12.20.
000005d4.00000610::2000/01/28-15:34:48.995 Network Name <Cluster Name>: DNS records for MYCLUSTER have changed. Attempting to reregister.
000005d4.00000610::2000/01/28-15:34:49.011 Network Name <Cluster Name>: Registered DNS name mycluster.reskit.com on IP Address 172.16.12.20.
CAUSE
This issue can occur because the network name resource builds a list of domain names to cluster Internet Protocol (IP) address mappings when you bring the name online. If the primary Domain Name Service (DNS) domain is the same as the adapter DNS domain, both entries get added to the list. This causes the resource to build two distinct DNS records that are used when registering the name with DNS. During the check period, the query returns only one record. The comparison to the stored records indicates a mismatch on the DNS server. The server does not detect the record, so it tries to register again.
RESOLUTION
To resolve this issue, do not set an adapter specific DNS name with the same name as the primary DNS Domain.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Additional query words: mscs
Keywords: kbenv kbnetwork kbprb KB252764
