Hello,
This topic has been discussed at least a couple of times in the past,
but is there currently any way to make NSD ignore out-of-zone data or
other errors in the zones or make NSD skip invalid zones? At least with
NSD 3.2.16 or earlier any such errors cause NSD rebuild fail and thus
prevent NSD from restarting.
This is especially problematic in environments where NSD acts as a slave
server for hundreds or thousands of zones. Because NSD needs to be
restarted every time a zone is added or removed, any errors in a single
zone make the whole restart procedure fail.
Antti
