Am 20.12.2017 um 16:59 schrieb Robert Blayzor:> I have been running NSD 4.x for quite some time.. Single master with multiple secondary slave servers. > > Everything has been running fine, currently on 4.1.19. > > On our slave servers, it seems that zones only AXFR to memory on the slave hosts? Never do they ever write the zones to disk even though we have specified a zonefile ? The server seems to operate ok and serves the zones out of memory, but zone files are never created on the slave server. > > Is there something that needs to be set to tell the slave server that AXFR zones from the master to write the zone files to disk ? or is there some reason why these files are not written? > > No errors in the logs and have verified that paths exist and are writable by the NSD user.running nsd chroot? zonefiles-write set to 0 in nsd.conf? also: do you use a database file? (I don't) I use to force the write to disc by "nsd-control write <zone>" and inspect the log immediately. Andreas
> On Dec 20, 2017, at 12:50 PM, A. Schulze <sca at andreasschulze.de> wrote: > > running nsd chroot? zonefiles-write set to 0 in nsd.conf? > also: do you use a database file? (I don't) > I use to force the write to disc by "nsd-control write <zone>" and inspect the log immediately.I am using the database file, and I do see that maybe it?s all being dump there. When enabling the database, does it no longer write the individual zone files? Database may be fine, so long as a saved copy of the zones are somewhere. We are not running chroot, and zonefiles-write is not set 0; no errors in log. So perhaps the database is it. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/