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).