round robin

[WebReactor Networks]

More to the point, BIND does not do any round-robining.  Period.  BIND simply returns both of the A records.  The client application chooses which of those A records to use.  In your case the "client application" is the Windows resolver.

See < http://www.isc.org/products/BIND/docs/bind-load-bal.html > for more info.

-------- Original Message --------
Subject: RE: round robin
Date: Fri, 15 Feb 2002 11:04:04 -0500
From: "Haygood, David" <david.haygood at pgnmail.com>
To: "'bind-users at isc.org'" <bind-users at isc.org>


If your Windows Desktop is 2K or XP its cache is 24 hours.

-----Original Message-----
From: Brian Noecker [mailto:bnoecker at jabber.com]
Sent: Wednesday, February 13, 2002 6:26 PM
To: 'bind-users at isc.org'
Subject: round robin



Is there a trick for round robin to work correctly?  I've got the following
scenario:

Two Bind 9.2.0 jailed servers, one master, one slave with either of the
following A record options:

test    10    A    10.2.2.1
test    10     A    10.2.2.2

or 

$TTL 2h

test     10    A    10.2.2.1
     10    A    10.2.2.2

Now, on the both servers, they use themselves as primary DNS in resolv.conf.
The master is on a solaris box, the slave a RH7.2 box.

When I'm on the master itself and ping test, 10.2.2.1 is the only answer I
get back.  When I'm on a windows desktop using the master as its DNS server,
I only get 10.2.2.1.  When I'm on the slave server and ping, I get about a
30/70 split on my returns.  

Should I expect consistency on the round robin nature of Bind?  

Thanks in advance.