[nsd-users] nsd-control delzone on a zone that is defined in the nsd.conf
jaap at NLnetLabs.nl
Wed May 8 21:32:51 UTC 2013
I am trying to wrap my head around the rationale of the restriction on not
allowing nsd-control to delzone a zone that is configured in the nsd.conf.
What is the risk here? Is it more of an operational one where it will not
truly delete if a stop/start of the daemon occurs without modification of
the nsd.conf? I mean, if your workflow is to always update your nsd.conf by
removing entries for zones you are planning to delzone (and then blowing
away the zone.list file before start) -- then where is the problem,
I see the restriction only exists in remote.c, and it doesn't look like
deleting one of these zones declared in the nsd.conf would be much
different that one that wasn't (although I am probably missing something).
Can you help me understand this, please?
FYI, Wouter is on vacation so it might take another week or so
before he answers. What I do remember from talking about this is
that "nsd-control delzone" is merely the inverse of "nsd-control
Zones defined in nsd.conf are supposed to be static that is why the
man nsd-control says:
Zones configured inside nsd.conf itself cannot be
removed this way because the daemon does not write to
the nsd.conf file, you need to add such zones to the
zonelist file to be able to delete them with the delzone
Hope this helps.
More information about the nsd-users