Am 30.08.2011 00:04, schrieb Mark Andrews:
In message 4e5b6098.80...@pernau.at, Klaus Darilion writes:
Hi!
I have 9.7.0-P1 as slave configured with two masters: M1 and M2. M2 is
currently down.
When M1 sends a NOTIFY to inform the salve of the new zone, bind starts
querying for the SOA
Am 30.08.2011 18:17, schrieb Klaus Darilion:
2. Thus, every 4.5 minutes the slave asks both masters for the serial.
The lookup to M1 works fine, the lookup to M2 of course fails as M2 is
down and thus bind starts with retransmissions: every lookup has 2
retransmissions every 15 seconds, then
-BEGIN PGP SIGNED MESSAGE-
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
Hi!
I have 9.7.0-P1 as slave configured with two masters: M1 and M2. M2 is
currently down.
When M1 sends a NOTIFY to inform the salve of the new zone, bind starts
querying for the SOA record at M2. As M2 is down, bind sends
retransmissions and tries it several times. It takes up to 2 minutes
In message 4e5b6098.80...@pernau.at, Klaus Darilion writes:
Hi!
I have 9.7.0-P1 as slave configured with two masters: M1 and M2. M2 is
currently down.
When M1 sends a NOTIFY to inform the salve of the new zone, bind starts
querying for the SOA record at M2. As M2 is down, bind sends
5 matches
Mail list logo