Caching server, forwarder list, dns failure

phn at icke-reklam.ipsec.nu phn at icke-reklam.ipsec.nu
Mon Jul 22 12:27:32 UTC 2002


Jean-Robert.Huon at alcatel.fr wrote:

> Hello,

> I looked in FAQ and archives, but I could not find any answer to my
> problem.

> We are running a caching only server with a "forwaders @ip-dns1
> @ip-dns2" line in the Named.boot file.

> @ip-dns1 and @ip-dns2 are the addresses of 2 DNS acting as main/backup
> servers.

> Everything is running well except when the "main" dns (e.g @ip-dns1)
> fails.

> When this failure occurs, and when a new name resolution is asked, Named
> tries normally the @ip-dns1 dns but seems to be "sticked" forever with
> it before to decide that this dns shall be down and that it has to try
> with @ip-dns2.

> I would be very interested to know if the behavior of Named upon such a
> failure is configurable in order that it decides to check the next dns
> in the forwarders list after a couple of seconds (time limit).

You seem to be running bind-4. 

Bind-8 ( current & recommended version 8.3.3 ) deals much better with 
multiple forwarders; it measures RTT of all forwarders and uses the
one that answers quickest. 


> Thanks in advance for any help

> regards 

> Jean-Robert


-- 
Peter Håkanson         
        IPSec  Sverige      ( At Gothenburg Riverside )
           Sorry about my e-mail address, but i'm trying to keep spam out,
	   remove "icke-reklam" if you feel for mailing me. Thanx.


More information about the bind-users mailing list