Report information
The Basics
Id:
44666
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:
(no value)
Severity:
(no value)
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
(no value)

Dates
Created:Fri, 10 Feb 2017 13:38:30 -0500
Updated:Tue, 25 Jul 2017 11:24:27 -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: minor logging bug in 9.10.4-P6: no "all zones loaded" and "running"
Date: Fri, 10 Feb 2017 13:38:22 -0500
To: bind-bugs@isc.org
From: "Anne Bennett" <anne@encs.concordia.ca>
I just upgraded bind from 9.10.4-P5 to 9.10.4-P6. After I stopped and started the service, I checked the syslog file in my usual way, looking for this: Feb 10 13:04:08 courage named[26517]: general: notice: all zones loaded Feb 10 13:04:08 courage named[26517]: general: notice: running On two of my five nameservers, those lines were present, but on the other three (which have a much larger number of zones), they were not. "rndc status" suggested that all five servers were happy, though. On the three which had not logged "all zones loaded" and "running", I issued "rndc reload", and that caused the missing lines to be logged. This is minor, of course, but since it might be an indication of something more serious, I thought it wise to report it. FWIW, all five servers use RPZ - I recall that the security advisory addressed by P6 was related to RPZ. If there's anything you'd like me to test, or additional information I should supply, let me know. Anne. -- Ms. Anne Bennett, Senior Sysadmin, ENCS, Concordia University, Montreal H3G 1M8 anne@encs.concordia.ca +1 514 848-2424 x2285