Report information
The Basics
Id:
45522
Status:
resolved
Priority:
Low/Low
Queue:

People
BugTracker
Version Fixed:
9.11.2, 9.12.0
Version Found:
9.11.1-P1
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
(no value)
Area:
bug

Dates
Created:Thu, 06 Jul 2017 16:48:56 -0400
Updated:Mon, 24 Jul 2017 02:34:46 -0400
Closed:Mon, 24 Jul 2017 02:34:46 -0400



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.

Date: Thu, 06 Jul 2017 20:48:56 +0000
From: cathya@isc.org
To: bind9-public@isc.org
Subject: Slaves using catalog zones mysteriously dropped them (responded REFUSED)
Slaves were found to be responding REFUSED to queries for zones they should have been authoritative for. There was no indication in the logs that they had dropped their catalogs. A stop/start on both slaves recovered their state, but it was noted during startup that they both reported syntax errors in the slave files for zones in the catalog. There was next to nothing in the logs to explain why the slaves stopped serving these zones. Could this be due to a misconfiguration, or something else?
I believe this is caused by the same underlying issue as #45310. Note that both slaves were reconfigured at 29-Jun-2017 22:13:30 and lots of "zone <name>: (slave) removed" messages appeared immediately afterwards.
Chuck Aurora confirmed in #45310 that the fix which is to be published in 9.11.2 works for him. Closing.