That's load balancing for a certain HOST that a client is trying to resolve
using the DNS server.
What I wanted to know was this: How do you load balance the DNS servers to
which your clients point, for name resolution? If you have 3 DNS servers,
and all your clients have in their TCP/IP settings to use the three DNS
servers as their preferred DNS servers, then the only reason a client would
use DNS server # 2, instead of DNS server # 1, is if DNS server # 1 does not
But, how can you tell the DHCP server to assign these 3 DNS servers to
clients in a random order, so that client # 1 might point to DNS server # 2,
and client # 2 might point to DNS server # 1?
> DNS uses a round-robin scheme that you can read about in microsoft's DNS
> whitepaper. Its really good and it answered quite a few on my questions
> > Microsoft keeps saying that you should have two or more DNS servers for
> > active directory, in order to provide redundancy and load balancing so
> > there is not just ONE dns server providing all the name resolution.
> > But, if all my clients are getting the DNS server settings from my DHCP,
> > it is set to give them 3 different DNS servers for their search order,
> > all my clients will always be attempting to resolve names using the
> > DNS server in their search order? Which defeats the whole
> > theory!
> > How do you set things so that some of your clients use a certain DNS
> > for their primary, and others use another as their primary?