• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 857
  • Last Modified:

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.

0
thehagman
Asked:
thehagman
  • 2
  • 2
1 Solution
 
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
 
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now