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

jasonsu at mail-central.com jasonsu at mail-central.com
Mon May 2 02:08:40 UTC 2016

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.
> I'd expect to see something in the logs with a permissions issue though...

I tried the strace, and TBH don't understand, yet, the output.  So I have some homework there.

Afaict, there's no perms-related error in my logs.  At least not that I recognize as being a perms-error.  If there were a perms problem, I'd have expected that 'rndc freeze' would report it -- I get no complaint.

I'm reading through as many posts as I can find -- Is there a specific/particular permission to check for?

Also, in LOGGING, right now I've got debug = on for all categories.  Really noisy, of course.

What specific logging category would report  perms problems ?  I'd like to turn just that one on .


More information about the bind-users mailing list