Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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

  • 10.1.1.0
  • 10.1.2.0
  • 10.2.0.0

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

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

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

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

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

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

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

share|improve this question

1 Answer 1

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 10.1.2.0 address ? If not, then you would need to configure a separate DNS server on the 10.2.0.0 subnet with the specific entries you desire.

share|improve this answer

Your Answer

 
discard

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.