Message-ID: In-Reply-To: Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 X-RT-Interface: Web Content-Disposition: inline MIME-Version: 1.0 Content-Transfer-Encoding: binary X-Mailer: MIME-tools 5.508 (Entity 5.508) References: RT-Send-CC: Content-Length: 845 On Wed Dec 13 23:03:15 2017, bconry wrote: > This suggests that the issue is in how the addzone is rolled back when a > zone fails to load. I have done additional testing and confirmed that the root issue is that the backing out of the zone due to it being unable to load (and probably some other conditions) is incomplete, with the zone remaining listed in view->nzf_config. This doesn't show up with only 'addzone' operations because 'addzone' uses the "optimization" of merely appending the new information to the existing file rather than rewriting the file from the nzf_config. I think it may be as simple as the '#ifndef HAVE_LMDB' block that adds the entry to the view's nzf_config being too soon. It ought to either be after the check for the zone being loaded or else logic needs to be added to the failure path to remove that data.