DNS Server Stops Using Round Robin for Host Name ResolutionLast reviewed: December 19, 1997Article ID: Q177883 |
The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
SYMPTOMSAfter you apply the latest Dns.exe, your Microsoft Windows NT Domain Name Service (DNS) server no longer responds to queries in a round robin fashion. For additional information, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q159310 TITLE : Updated Version of Dns.exe Fixes Several Problems ARTICLE-ID: Q168321 TITLE : Creating a DNS Record for a Host That Has 2 or More IP Addresses CAUSEThe latest version of Dns.exe for Windows NT server introduces a new feature, LocalNetPriority, that attempts to return Host resources that are local to the requestor instead of merely responding round robin.
RESOLUTIONBy default, this feature is enabled and normal round robin responses will not occur. To return to round robin responses, you will need to use the following steps to disable the LocalNetPriority setting: WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.
MORE INFORMATIONThe DNS server will attempt to offer the "best-fit" address in response to a DNS query. This best-fit is one that is determined to be on the same subnet as the requesting DNS Client. The classfull address is used to determine if the record and the querying DNS Client are on the same subnet. This means only the first octet will be used for class A addresses, the first two octets for class B, and the first three octets for Class C addresses. If you have subnetted your address space, this may have a derogatory effect on round robin load balancing. Keywords : nthowto ntnetserv NTSrv kbnetwork Version : WinNT:4.0 Platform : winnt Issue type : kbprb |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |