On Thu, Sep 24, 2026 at 11:26:10AM CEST, Daniel Salzman via knot-dns-users
<knot-dns-users(a)lists.nic.cz> said:
Hi Erwin,
Sorry, I don't understand why it breaks zone transfers when the serial is higher.
Could you show me the zone configuration? We only changed `zonefile-load:
difference'.
Daniel
Sorry, first message sent with only half of the answer. Let me explain the break
we begin with serial synchronized on Sep 11 master and slave have serial 2026023146
After upgrade, knot is restarted on slave, and uses 2026091100 as serial for the zone
Master then re-signs the zone, set serial on master to 2026023147 and notifies slave
On slave I have the log :
Sep 12 03:23:42 ns knot[32256]: info: [domain.] notify, incoming, remote ns.domain@53694,
serial 2026023147
Sep 12 03:23:42 ns knot[32256]: info: [domain.] refresh, remote ns.domain@53 TCP, remote
serial 2026023147, remote is outdated
Sep 12 03:23:42 ns knot[32256]: warning: [domain.] NOTIFYing master is outdated
And thats completely logic since master notifies for serial 2026023147 and slave has
serial 2026091100
What happened is that after several days, the RRSIGs served by slave where expired (they
had not been updated)
--
Erwan David