Report information
The Basics
Id:
45279
Status:
new
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
(no value)
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
BIND Server
Area:
bug

Dates
Created:Tue, 23 May 2017 13:24:50 -0400
Updated:Tue, 25 Jul 2017 11:17:58 -0400
Closed:Not set



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: Bind is not sending NOTIFYs when increasing the serial with rndc signing -serial
Date: Tue, 23 May 2017 17:24:38 +0000
To: "bind9-bugs@isc.org" <bind9-bugs@isc.org>
From: "Klaus Darilion" <klaus.darilion@nic.at>
Tested with Bind 9.11.0-P5: From the 9.11.0 changelog: "The serial number of a dynamically updatable zone can now be set using rndc signing -serial number zonename. This is particularly useful with inline-signing zones that have been reset. Setting the serial number to a value larger than that on the slaves will trigger an AXFR-style transfer." An AXFR-style transfer will only be triggered if Bind does send NOTIFYs after the serial was increased with "rndc signing -serial". But this is unfortunately not the case. We do work around this issue by manually triggering them with "rndc notify". But IMO it is a bug that Bind is not sending NOTIFYs by himself after increasing the serial. Thanks Klaus