Round robin is supported in bind 4.9.3 and above

A couple of URL's for DNS info 
	http://www.dns.net
	http://www.nominum.com/resources/bind-faq.html

The best source of info would be OReily's book DNS/Bind Third edition (covers upto 8.x.x)


As far as DNS round robin working with NT, DNS on NT is a different animal
MS implimentation of DNS is primarily based on NetBios, and  and which I do not
know a whole lot about DNS and MS products. 

Here is a quick run down on how to configure round robin.

let's say you want to round-robin the name www.foo.com to 5 IP addrs so as to 
load share the http traffic to 5 actual machines.  You could set up "A" records

in dns that look like:

www.foo.com.    IN      A       192.9.9.1
www.foo.com.    IN      A       192.9.9.2
www.foo.com.    IN      A       192.9.9.3
www.foo.com.    IN      A       192.9.9.4
www.foo.com.    IN      A       192.9.9.5

With just this alone, every time the nameserver gets a request for the A
records 
for www.foo.com it will alter the order of the rely for example the first time 
the data is requested, it will return:

192.9.9.1 192.9.9.2 192.9.9.3 192.9.9.4 192.9.9.5

the next time it will send back:
192.9.9.2 192.9.9.3 192.9.9.4 192.9.9.5 192.9.9.1
the next:
192.9.9.3 192.9.9.4 192.9.9.5 192.9.9.1 192.9.9.2

and so on.

FYI.. There is no health checking of returned IP's. So if a server is down
there is a possible chance that the downed servers IP will be returned, this
is do to round robin being serial in nature.


Things to remember:

This is IMPORTANT:

host caching defeats round-robin places this can occur other nameservers, 
ypserv, nscd, etc.
	You may need to turn of nscd, there has been reports that round robin 
	will not work if nscd is running.

you may want to shorten the ttl on those specific records and no the whole db 
file.  To do this, you can add the ttl val before the "IN" in the record, don't

forget to put the default ttl back on the next record that isn't involved in
the 
round-robin or the ttl will be carried to those records as well.
Suns may not do what you want them to do if the first IP addr returned doesn't 
appear to be the closest.  In other words, just because the the resolver sends 
back an answer (from a nameserver) in a certain order, it doesn't mean an 
application has to use the first IP addr it was given.