No subject

Highlights of BIND 8.2.3
Several serious security holes plugged. 
Many bug fixes, especially to IXFR and TSIG. 
New "ndc reload -noexpired" feature. 
"ndc status" now shows config file name and age. 
Ignore stuck stale queries after long zone load delay. 
TTL 0 is now allowed in zone files. 
Several updated contrib/ packages. 
Better portability to Win/NT. 
Ported to Darwin (Mac OS X). 
**** Forwarders are now used in order by measured RTT. *****

I remember seeing some postings on the bind-isc mailing lists that there were 
some bugs in the forwarder code in 8.2.2 (maybe even from Cricket?), you should 
upgrade to 8.2.3 but I don't think you'll get the desired result anyway if 
you're looking to load balance the requests across those two nameservers.

I don't think forwarders ever round-robin'ed properly (thus the need for the 
bugfix in 8.2.3 to make them do RTT calculations by default).

Nate

Quoting Steve Pollock <bouldertri at yahoo.com>:

> Having some trouble with this one.  (this is in a lab)
> 
> Want to have two servers authoritative for
> www.bouldertri.net.  Main server has bouldertri.net
> and a number of hosts.  Works fine for the first host
> in /etc/named.conf, check the fowarders for
> www.bouldertri.net:
> 
> cat /etc/named.conf
> options {
>         directory "/var/named";
>         forwarders{
>         };
> };
> zone "." {
>         type hint;
>         file "named.ca";
> };
> zone "bouldertri.net"{
>         type master;
>         file "bouldertri.net";
> };
> zone "0.0.127.in-addr.arpa"{
>         type master;
>         file "named.local";
> };
> zone "1.168.192.IN-ADDR.ARPA"{
>         type master;
>         file "192.168.1";
> };
> zone "www.bouldertri.net"{
>         type forward;
>         forward only;
>         forwarders{
>                 152.131.87.3; 192.168.1.204;
>         };
> 
> And I have two ns records as well:
> 
> cat bouldertri.net
> @               IN      SOA     boulder2       
> hostmaster.boulder2. (
>                         17 ; serial
>                         3600 ; refresh
>                         900 ; retry
>                         1209600 ; expire
>                         43200 ; default_ttl
>                         )
> @               IN      MX      5       boulder2
> @               IN      NS      boulder2
> ;
> ;Hosts -- Address records
> boulder2                IN      A       192.168.1.202
> boulder1                IN      A       192.168.1.201
> bm              IN      A       192.168.1.203
> ;
> ;NameServer Records, point www at the CSS switch
> www.bouldertri.net.             IN      NS     
> 192.168.1.204.
> www.bouldertri.net.             IN      NS     
> 152.131.87.1.
> ;
> ; CNAME or Alias Records
> rh              IN      CNAME   boulder2
> md              IN      CNAME   boulder1
> 
> 
> Yet...  dig @192.168.1.202 www.bouldertri.net always
> returns the same address and always goes to the same
> forwarder.  I had expected it to roundrobin between
> the two...
> 
> Ideas?
> 
> -Steve
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail. 
> http://personal.mail.yahoo.com/
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 



--
Nate Duehr, nate at natetech.com

"Never underestimate the bandwidth of a 747 filled with CD-ROM's."