Hey Steve, Thanks for the response. I actually found the solution. It turns out that the .jnl files are not the only ones that get modified when using DDNS. Performing a chown -R for named:named on /var/named/master fixed the problem. The actual zone data file, db.home.lan, also gets reformatted in the process, with the new entries. That seems a bit odd to me, I would have thought the whole point of the journal file is preventing the main datafile from being reformatted or changed.
Thanks so much, Andrew On Sep 20, 2014, at 5:18 PM, Steve Shockley <[email protected]> wrote: > On 9/20/2014 1:46 PM, Andrew Lester wrote: >> Does anybody know what I can do to make the zone journal file be accessible >> by named? > > It's been a while since I set it up, but I gave up and made /var/named/master > owned by named. I also had to set managed-keys-directory "/master" in the > config so managed-keys.bind and managed-keys.bind.jnl were writable. I found > ktrace to be helpful for debugging as well. I probably should have > documented everything I did...
