Bug 580 - Valid zone with bogus-directory configuration (silently) removes zone-data from slaves.
Valid zone with bogus-directory configuration (silently) removes zone-data fr...
Status: RESOLVED FIXED
Product: NSD
Classification: Unclassified
Component: NSD Code
3.2.x
Other Linux
: P5 trivial
Assigned To: NSD team
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-21 21:58 CEST by carl.hasselstrom
Modified: 2014-06-17 11:31 CEST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description carl.hasselstrom 2014-05-21 21:58:33 CEST
Hi !

zone:
       name:example.com
       zone:foo/example.com

In the case of foo not existing under zones/ the slave will happily provide you with authoritative answers from mem, until moment its written to disk (since it can't).

This is obviously visible when trying "nsdc patch" but, unless thats done, it will work for roughly 24h.

I can't find find anything in my nsd logs regarding the zone and the actual event.
Comment 1 Matthijs Mekking 2014-06-17 11:31:46 CEST
Hi Carl,

Thanks for your report. Normally you would see these errors because nsd-patch is ran in something like cron and cron will mail you the stderr output in case of problems.

I have added similar code in NSD3 that is in NSD4: It will create the base directories of the zone file if they do not yet exist. This may still cause nsdc patch to fail though: for example when the permissions are wrong.