On 30.01.2014 14:28, Tony Finch wrote:
Mark Andrews ma...@isc.org wrote:
In message 52ea4c56.5060...@pernau.at, Klaus Darilion writes:
Are there any tools/ways to query Bind for the incoming serial?
rndc zonestatus zone [class [view]]
I think that's a BIND-9.10 feature
Same problem with:
# named -V
BIND 9.9.4-P1
On 11.12.2013 13:39, Klaus Darilion wrote:
Hi!
# named -V
BIND 9.9.3-rl.13204.02-P2
I have configured slave zones with inline signing:
zone mydomain.at {
type slave;
file /etc/bind/mydomain.at;
masters { 1.2.3.4
Hi!
I have several bind instances running on the same host. All of them use
the same logging prefix, e.g:
named[11926]: zone mydomain/IN: Transfer started.
named[11926]: transfer of 'mydomain/IN' from 2.3.4.5#53: connected using
2.3.4.5#44224
named[13479]: client 2.3.4.5#44224: transfer of
On 02.07.2013 14:59, Tony Finch wrote:
Klaus Darilion klaus.mailingli...@pernau.at wrote:
Some software allows to configure the syslog prefix, but I couldn't find that
for bind.
Rename the named executable.
I would prefer a configuration options, but I guess I have to use
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
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
101 - 107 of 107 matches
Mail list logo
