Multi-Homed DNS Server Problems

[cnull]

Here is the situation:

We have a backend network running for our servers. It is used for backups, large file transfer etc...

We also have our normal network that is used for all of our clients to connect to AD, File Serving, Applications etc...

We were having a problem where DNS would pass both network IP addresses to everyone causing some extremely slow booting and logon as well as application problems.
Here is the setup:
Backend network is 192.168.1.0
Server room 13th floor is 132.10.32.0
12th floor is 132.10.22.0
11th floor is 132.10.12.0
Outstation#1 146.165.17.0
Outstation#2 146.165.210.0

All of our servers that are on the backend network are registering in DNS with two Host(A) resource records. One is the 192.168.1.0 network and the other is the 132.10.32.0 (13th floor) Address.

We enabled subnet prioritizing so that clients that are on any of the 132.10.x.X subnets get the correct ipaddreses (i.e. 132.10.X.X)fixing the original problem, but then the 146.165.x.x clients began to get the 192.168.1.0 ip addresses back for the servers. This is causing considerable slowing on thier end.

Here is the Question!! -->> I need to know how to set the 192.168.1.0 ip addresses to only be sent to the servers on the backend network.

NOTE: We specifically set the subnet prioritizing to check for class B rather than the class C subnet because Class C did not work at all. This is the command that we used... Dnscmd /Config /LocalNetPriorityNetMask 0x0000FFFF
see:

http://support.microsoft.com/?kbid=842197

Thanks in advance for any help you can provide!!
Chris

 

[ShackDaddy]

This is complicated. I don't think there are DNS settings that will get you around the issues you describe. I would either be setting up an extra DNS server just for the systems with backend connections and manually creating entries for them in the DNS that the rest of the company uses, or I would stick with the single DNS but not allow those systems to auto-register with DNS, instead I'd create their A-records manually and not create records for the backend adapters. Then I would create a single custom host-file and place it on each of the servers that has a connection to the backend network.

I know you've probably already considered and rejected these ideas for their potential for maintenance headaches, but that's the setup that would smooth out this issue.

 

[cnull]

Yeah we considered all of that, but we figured that MS was smart enough to have a solution. I am leaning toward a second DNS server separate than the frontend DNS. Thanks for your input!
Chris

Anyone else want to pipe in, please do so!!