Re: also-notify and nsupdate doesnt work

2016-05-01 Thread Matthew Pounsett
On 1 May 2016 at 23:57, wrote: > hi, > i have a setup with one normal and some hidden slaves. > i set up a zone with also-notify and all worked fine. > all slaves got notifies and updates. > now i added a key and policy to remote update the zone. > the updates with nsupdate woks fine. > but the n

also-notify and nsupdate doesnt work

2016-05-01 Thread jonny
hi, i have a setup with one normal and some hidden slaves. i set up a zone with also-notify and all worked fine. all slaves got notifies and updates. now i added a key and policy to remote update the zone. the updates with nsupdate woks fine. but the notify is only sent to the slave, but not to th

Re: 'succesful' nsupdate of remote server not persistent across nameserver restart?

2016-05-01 Thread jasonsu
On Sun, May 1, 2016, at 11:34 AM, Phil Mayers wrote: > Days? That surely must be permissions? > > As per my other email - attach a strace to the bind process, and run > "rndc sync" / "rndc freeze" to force an immediate write-out - if there's > a permission problem the error should be apparent. >

Re: 'succesful' nsupdate of remote server not persistent across nameserver restart?

2016-05-01 Thread Phil Mayers
On 01/05/16 19:15, jaso...@mail-central.com wrote: On Sun, May 1, 2016, at 11:05 AM, Phil Mayers wrote: IIUC, though, a nameserver restart is supposed to force the write-to-journal immediately, right? No, I don't think so. Perhaps the behaviour in flush-zones-on-shutdown (which defaults to

Re: 'succesful' nsupdate of remote server not persistent across nameserver restart?

2016-05-01 Thread Phil Mayers
On 01/05/16 19:05, Phil Mayers wrote: On 30/04/16 04:49, jaso...@mail-central.com wrote: Hi On Fri, Apr 29, 2016, at 08:42 PM, Mark Andrews wrote: Just give it time. The zone contents are the masterfile + journal. The masterfile only gets written periodically as it can be a expensive operatio

Re: 'succesful' nsupdate of remote server not persistent across nameserver restart?

2016-05-01 Thread jasonsu
On Sun, May 1, 2016, at 11:05 AM, Phil Mayers wrote: > > IIUC, though, a nameserver restart is supposed to force the > > write-to-journal immediately, right? > > No, I don't think so. > > Perhaps the behaviour in flush-zones-on-shutdown (which defaults to > "no") is what you're thinking of? >

Re: 'succesful' nsupdate of remote server not persistent across nameserver restart?

2016-05-01 Thread Phil Mayers
On 30/04/16 04:49, jaso...@mail-central.com wrote: Hi On Fri, Apr 29, 2016, at 08:42 PM, Mark Andrews wrote: Just give it time. The zone contents are the masterfile + journal. The masterfile only gets written periodically as it can be a expensive operation. Sure, under normal operation, as I