faster fail-over between multiple masters

Michael Graff mgraff at
Tue Aug 30 18:33:42 UTC 2011

Hash: SHA1

On 2011-08-30 12:06 PM, Klaus Darilion wrote:

> Unfortunately I fail to find the options where I can configure the 
> number of retransmissions, timeouts and number of transactions -
> please give me some hints.

I don't believe there are external knobs for this behavior.

I can think of several possible fixes here:

(1)  if we get a notify during a SOA check, proceed as usual but flag
this so we will just start another SOA check.  We may transfer the
zone between these checks (and probably should.)

(2)  send all SOA requests in parallel, and use an overall max time to
wait (perhaps 20 seconds) and re-send the SOA to servers which have
not responded every 4 seconds.  This limits the total time an SOA
check will take.

(3)  If any of the servers respond with better SOA serial numbers than
we have, transfer from the masters as listed in the config file or
whichever is better, depending on current behavior.

I do not know when we would be able to get to this change, but I'll
put them on the back-log for future releases.

If you want to go code diving, you can likely find the timeouts and
change the behavior for your servers.  However, you'll have to track
this each time we do a release for the foreseeable future.

- -- 
- --Michael

ISC offers support on many of its products, including BIND 9.  If you
depend on it, depend on us!
See for all the details.
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla -

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mgraff.vcf
Type: text/x-vcard
Size: 308 bytes
Desc: not available
URL: <>

More information about the bind-users mailing list