describes how to use netmask ordering with Windows 2003 DNS server.
It is even possible to change the netmask to determine what is a near IP.
However, I don't see what to do in a mixed netword.
Network 1 = 10.0.0.0/23
Network 2 = 10.0.2.0/23
Network 3 = 10.0.3.0/23
and A records for myhost.example.com pointing to 10.0.0.123, 10.0.2.123, 10.0.3.123
With default netmask (i.e. class C), netmask ordering works for networks 2 and 3, but not for 1:
A host 10.0.1.x/23 would not be considered matching any of the A records, hence would obtain a random order
With a changed netmaskd of /23, things work for network 1, but not for 2 and 3:
For host 10.0.2.x both 10.0.2.123 and 10.0.3.123 would be considered nearby
Is there a way to associate different networks with different netmasks for the purpose of netmask ordering?
My current workaround is to use secondary ip addresses (i.e. 10.0.0.123 gets a secodary address 10.0.1.123 bound to its interface and a corresponding A ercord is entered)
I simply don't like the need for secondary IPs.