Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a network with three subnets accessing a DNS server running on Windows Server 2008:


The DNS server is on both the network and the network.

Most of the clients are on the and the subnets such any client can access any other client on either subnet. Those clients are just fine.

The clients on are the issue. Clients on only have access to the subnet and not the subnet.

As I understand it, if a client on the subnet requests a client that has all three addresses, the DNS will prioritize the address over the others.

However, when a client requests a client that has only a and address, it does a RoundRobin guessing algorithm.

The issue that is happening is that a request from a client to a client on both the and subnets is resolving to a address instead of a address.

Is there a way to tell the DNS: "If a request comes from, prioritize the addresses."?

share|improve this question

I dont believe so.
By default Microsoft DNS will respond with the 'nearest' server to the machine the request came from, though you can force it to use standard round-robin through a registry change.

For the issue you are having though, can you not just remove the DNS entry for the address ? If not, then you would need to configure a separate DNS server on the subnet with the specific entries you desire.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.