if bindbackend has loaded a zone assuming it is NSEC, and somebody sets NSEC3PARAM in the zone metadata, until r2819, bindbackend could go into a lockup because it gets an NSEC3 ordername question while all the NSEC3 fields inside bindbackend are empty.
r2819 avoids the lockup (making sure we only wrap around the whole NSEC3 field list once) but does not fix the underlying issue.
As bindbackend is the one providing pdns_server the NSEC3PARAM metadata anyway, bindbackend should be able to trigger a zone reload at that point.
Avoid metadata mixup in some slaving cases. Patch by Kees Monshouwer,…
… closing #603
git-svn-id: svn://svn.powerdns.com/pdns/trunk/pdns@2834 d19b8d6e-7fed-0310-83ef-9ca221ded41b
underlying issue fixed in r2834