[Yeti DNS Discuss] A weird behavior of Knot

Paul Vixie paul at redbarn.org
Fri Aug 14 13:24:14 UTC 2015

Carsten Strotmann wrote:
> Hi,
> Davey(宋林健) wrote:
>> Hi all, 
>> We observed a weird behavior of Knot when we reset the .arpa ns records
>> to [a-m].root-servers.net <http://root-servers.net> in root zone file. 
>> The knot root server (yeti-dns01.dnsworkshop.org
>> <http://yeti-dns01.dnsworkshop.org>)  entered a a kind of "hung” state
>> after updating the root zone (with a new serial number) but without
>> change of the NS records list for .arpa.  
> some additional information: the Knot-DNS version running at the time
> was 2.0.0-r1. It has since been updated to 2.0.0 (the release version).
> The weird behavior seen might have been an artifact of the
> release-candidate version.

it's also worth testing online child zone removal in the new version. in
bind4, a server that was authoritative for both dec.com and pa.dec.com
would serve a damaged dec.com after the pa.dec.com zone was removed
online (by "ndc reconfig"). the fix we used was ugly-- we just reloaded
all parent zones of any removed zones.

knot may have similar problems. it's worth a specific test in the
release version, even if yeti does not anticipate any more zone removals
(since we only have one zone left.)

Paul Vixie

More information about the discuss mailing list