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

People
Owner:
Nobody in particular
Cc:
AdminCc:

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:22:40 -0400
Updated:Tue, 25 Jul 2017 09:09:55 -0400
Closed:Tue, 25 Jul 2017 09:09:55 -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.

From: cathya@isc.org
Date: Thu, 06 Jul 2017 20:22:40 +0000
Subject: Catalog zones add operations use a random zone name when logging
To: bind9-public@isc.org
When logging catz add operations (but apparently not deletes) BIND will pick a random zone name from the catalog and use it for every log entry in that transaction. The name picked doesn't have to be one of the names involved in the transaction.. it may be any name in the catalog. BIND 9.11.1-P1 on centos-release-7-3.1611.el7.centos.x86_64 For example: 29-Jun-2017 01:02:27.993 general: info: zone catalog.db/IN: Transfer started. 29-Jun-2017 01:02:28.004 general: info: catz: updating catalog zone 'catalog.db' with serial 5 29-Jun-2017 01:02:28.004 general: info: zone catalog.db/IN: transferred serial 5: TSIG 'master1-slave2' 29-Jun-2017 01:02:28.006 general: info: catz: adding zone 'zone1.example.com.catalog.db' from catalog 'catalog.db' - success 29-Jun-2017 01:02:28.006 general: info: catz: adding zone 'zone1.example.com.catalog.db' from catalog 'catalog.db' - success 29-Jun-2017 01:02:28.006 general: info: catz: adding zone 'zone1.example.com.catalog.db from catalog 'catalog.db' - success 29-Jun-2017 01:02:28.006 general: info: catz: adding zone 'zone1.example.com.catalog.db' from catalog 'catalog.db' - success 29-Jun-2017 01:02:28.006 general: info: catz: adding zone 'zone1.example.com.catalog.db' from catalog 'catalog.db' - success ... This also occurs when adding a singleton new zone to the catalog some time after named has started up. It also happens when making large scale changes (multiple zones).
Added a missing dns_name_format() call to one of the loops inside dns_catz_zones_merge(). Updated catalog zones system test to ensure proper logging of added member zone names. While investigating why this issue has not been caught earlier, I also found out that the catalog zones system test was improperly handling waiting for multiple log messages in named.run: every time the system test expected two log messages to appear, timing out while waiting for one of these messages was effectively not considered an error as long as the other message appeared in the log as expected. All instances of this problem were fixed and it did not cause the system test to detect any further issues. All the above fixes are in the rt45520 branch, please review. They will need to be cherry-picked into v9_11 as well.
On Thu Jul 06 21:42:14 2017, michal wrote: > Added a missing dns_name_format() call to one of the loops inside > dns_catz_zones_merge(). Updated catalog zones system test to ensure > proper logging of added member zone names. > > While investigating why this issue has not been caught earlier, I also > found out that the catalog zones system test was improperly handling > waiting for multiple log messages in named.run: every time the system > test expected two log messages to appear, timing out while waiting for > one of these messages was effectively not considered an error as long as > the other message appeared in the log as expected. All instances of > this problem were fixed and it did not cause the system test to detect > any further issues. > > All the above fixes are in the rt45520 branch, please review. They will > need to be cherry-picked into v9_11 as well. Looks fine.
4649. [bug] The wrong zone was logged when a catalog zone is added. [RT #45520]
Subject: Re: Catalog zones add operations use a random zone name when logging [ISC-Bugs #45520]
Date: Tue, 11 Jul 2017 06:14:08 -0500
To: bind9-public@isc.org
From: "Chuck Aurora" <ca-isc@nodns4.us>
Mark Andrews via RT wrote: > 4649. [bug] The wrong zone was logged when a catalog zone is added. > [RT #45520] Tested and seems to be fixed. All 17 catalog member zones were logged with "catz: adding zone" lines at startup. -- Chuck