On 09/20/2014 10:33 PM, Andrew Lester wrote:
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
The journal is just to keep track of changes until they can get written
to the zone file. The journal here works the same way as a filesystem
journal or transaction journal in a database. An 'rndc sync -clean'
will write updates to the zone file and remove the .jnl file so having
permissions to update the zone file, .jnl file , as well as create a new
.jnl file inside the directory should all be required.
-Jason
