Note The round robin feature of DNS makes it possible for DNS to return the IP addresses of a name in a different order every time.
- You have eight type A records for the same DNS name.
- Each of your eight type A records has a separate address.
The round robin feature is used to randomize the results of a similar type of query to provide basic load-balancing functionality. In the earlier example, eight type A records with the same name and different IP addresses cause a different answer to be prioritized to the top with each query. Because a new IP address is prioritized to the top with each query, clients are not repeatedly routed to the same server.
The initial release of Windows 2000 Server cannot natively use the netmask ordering feature and the round robin feature at the same time. If the netmask ordering feature is turned on, the answers are always provided to the clients in the same order. In Windows Server 2003, this behavior changed to permit the use of both the subnet-based netmask ordering feature and the round robin feature. The use of both the netmask ordering feature and the round robin feature provides proximity awareness and load-balancing.
In many current network environments, it is uncommon to have a subnet mask that is native to the actual address. Therefore, netmask-ordering that is based on the native class of an IP address is unreliable in predicting whether a network is local. Windows Server 2003 bases proximity on Class C regardless of the native address class.
For example, a company is assigned a 126.45.x.x subnet. It is unlikely that an eight-bit subnet mask will be used to define this subnet in their internal network. Additionally, the company owns only part of the class A subnet. Because this range will likely be divided into class B or smaller networks, netmask ordering may not return results that are close to the client. This is true if the network configuration is different from the network configuration that is implied by the native class of address. Because Windows Server 2003 bases proximity on Class C, close resources are more discoverable.
You can use the Dnscmd /Config /LocalNetPriorityNetMask 0x000000FF Dnscmd.exe command to restore Windows Server 2003 settings to the default settings.
Although the default setting in Windows Server 2003 is to base proximity on Class C, you can change this setting. You can define what part of the mask is relative for netmask ordering based on your environment. When you issue the /LocalNetPriorityNetMask switch, you can specify the bits that are significant to the netmask ordering operation. You can use the Dnscmd /Config /LocalNetPriorityNetMask 0x0000FFFF command to use class B ( or 16 bit) for netmask ordering.
The following table lists other netmask ordering settings:
The significant bits set what part of the address is the host space. Because the binary equivalent of 0x3 is 11 and the binary equivalent of 0xF is 1111, 6 bits are set as part of the host address. If seven bits (255.255.255.128 or /25) are required, the value would be 0x0000007F because the binary equivalent of 0x7F is 0111 1111. If only five bits (255.255.255.224 or /27) are required, the value would be 0x0000001F because the binary equivalent of0x1F is 0001 1111.
The Dnscmd /Config /LocalNetPriorityNetMask 0xFFFFFFFF command configures Windows Server 2003 to use round-robining and netmask ordering based on the client native IP address class.
Article ID: 842197 - Last Review: Mar 29, 2017 - Revision: 4