Flexible netmask ordering with Windows 2003 DNS server?

http://support.microsoft.com/kb/842197
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.
Consider this
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.

LVL 20
thehagmanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris DentPowerShell DeveloperCommented:

Afraid not, at least not without maintaining different LocalNetPriorityNetMask values on different DNS servers. It's either match on /23 or match on /24 in this case.

It would be really nice if some of the features available to BIND made their way onto MS DNS.

Chris
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
thehagmanAuthor Commented:
EDIT:
I meant to write

Network 1 = 10.0.0.0/23
Network 2 = 10.0.2.0/24
Network 3 = 10.0.3.0/24

I hope tzhis dis not cause confusion
0
Chris DentPowerShell DeveloperCommented:

I thought that might be the case, you're not normally prone to simple errors :)

Unfortunately my original statement still stands.

Chris
0
thehagmanAuthor Commented:
Simple errors as "tzhis dis", you mean?  ;)

I won't try to maintaining different LocalNetPriorityNetMask values on different DNS servers - in the end you never know who asks who.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.