Hi all,
From KNET , I notice there is a topic about opendnssec High Availablity at
https://wiki.opendnssec.org/display/DOCS/High+availability
But I was a little puzzled by this page.
It mentioned about master/slave like this:
Master/Slave
Careful consideration should be given to which, if
Hi,
On Sun, Aug 24, 2014 at 3:59 PM, gaolei gao...@knet.cn wrote:
Hi all,
From KNET , I notice there is a topic about opendnssec High Availablity at
https://wiki.opendnssec.org/display/DOCS/High+availability
But I was a little puzzled by this page.
It mentioned about master/slave
Hi Patrik,
My first guess would be that there are old signer configuration files
and other files in `/var/opendnssec/signconf/` and
`/var/opendnssec/tmp/` that cause this.
Can you share the kasp.xml? It seems you don't use the default policy,
because the core dump shows it is adding NSEC
Hello Matthijs,
Thank you for looking at this, see my comments inline.
On Sun, Aug 24, 2014 at 05:33:13PM +0200, Matthijs Mekking wrote:
My first guess would be that there are old signer configuration files
and other files in `/var/opendnssec/signconf/` and
`/var/opendnssec/tmp/` that cause
Hi,Emil
From the previous thread discussion in
http://lists.opendnssec.org/pipermail/opendnssec-user/2014-June/003024.html , I
notice the idea is like this :
1. the master runs enforcer and signer
2. the slave runs signer only
3. sync conf files from master to slave
4. if master is down , run
