PrioritizeRecordData
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
| Data type | Range | Default value |
|---|---|---|
REG_DWORD |
0 | 1 |
1 |
Description
Specifies whether the DNS client, upon receiving an answer to a DNS query, looks for the address most similar to its own, when there are multiple addresses in the answer to its query. By choosing the address most like its own, the client connects to the server nearest to it on the network, which reduces network traffic. When the value of this entry is 1, the client prioritizes for the nearest address; when the value is zero, the client attempts to connect to the first address in the answer.
Note
This scheme attempts to reduce network traffic by connecting clients with local IP addresses. This registry entry controls whether the client prioritizes addresses, but Windows Server 2003 DNS server can also be configured to prioritize the addresses in its answers according to their similiarity to the address of the requesting client. This behavior by Whister DNS server is controlled by the value of LocalNetPriority.
Subnet prioritization, whether configured on the client or the server, nullifies the load-balancing benefits of round-robin name resolution. Round-robin name resolution is a scheme by which the server rotates the order of the addresses in its answers to spread connection loads across all applicable servers. By default, Windows Server 2003 DNS service uses round-robin name resolution. For more information about subnet prioritization and round-robin name resolution, see the TCP/IP Core Networking Guide of the Microsoft Windows Server 2003 Technical Reference .