8 Úno
2016
8 Úno
'16
14:03
On 08/02/16 13:41, Jan Včelak wrote:
Hello Jan,
Ah, I had guessed this was the cause. Knot shouldn't have to do any
queries, because in the config, I have:
server:
identity: ns1.nl-ams.testdns.ripe.net
nsid: ns1.nl-ams.testdns.ripe.net
The values are explicit, so there should be no lookups. The lookup is
only necessary if the values are set to "yes". And even then, just once
should be enough (at start, or at reload).
Ooh, I give up :)
I think the refresh batching may be due to the host name lookups I noted
earlier. I don't have any more to add for now.
Regards,
Anand
Thank you for a complex write-up. :)
You're welcome!
Note that
118-second delay before the zone refreshes start. Note that
during this delay, Knot made hundreds of DNS queries (A and AAAA)
towards the locally-configured caching resolver (Google DNS in this
case) for its own hostname, for example:
Yes, this is a bug. Knot tries to get host's canonical name for the
purpose of hostname.bind TXT/CH queries. This happens when any event is
started, which is wrong. We will fix it. Any outgoing queries are handled by some kind of a
state machine. And we
use layers to stack the processing steps. So this error just means that
there was some error during the transfer.
We could improve this. But probably no earlier than in 2.2.0.
Hm, okay. I had hoped you could fix this for 2.1.1, but I guess you're
eager to release 2.1.1 this week.
We will improve the documentation before the release.
And we will try to
Thanks!
About
"zone-sign": the word "resign" usually means "leave your
job", so
it's probably best spelled as "re-sign" for clarity :)
I already resigned on naming commands. ;-) This one was originally named
'sign'. But we changed it since we do automatic signing and this command
just forces Knot to drop all existing signatures. I think Knot
2's slave zone refresh strategy and timing need still more
work, if it's to work effectively for a configuration with lots of slave
zones.
The thing is that we didn't changed anything on the transfer scheduling
between 1.6 and 2.0. I'll investigate this. If you found some additional
hints, please, let us know.