RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Adding zones to same file in slave server results in error


Version-Release number of selected component (if applicable):

 9.11


How reproducible:

Always

Steps to Reproduce:
1. Add same file to different zones in slave server
2. Start bind server
3. named service doesn't start

Actual results:

writeable file 'slave/zone1.txt': already in use: name.conf:1221
writeable file 'slave/zone2.txt': already in use: name.conf:1285
writeable file 'slave/zone3.txt': already in use: name.conf:1391
...

Expected results:

named service should start normally and not die

Additional info:

https://www.mail-archive.com/bind-users@lists.isc.org/msg20553.html

In bind 9.11 and later, in-view VIEWNAME can be used to share common data. It saves the bandwidth, memory and files.

Could be used this way:

view "public" {
  # ...
  zone "some.example.org" {
    type slave;
    masters { 10.1.1.1; };
    file "some.example.org.db";
  };
};

view "private" {
  # ...
  zone "some.example.org" {
    in-view "public";
  };

};

It is not possible on BIND 9.9 in RHEL 7.6 and RHEL 6, unique names for each writeable zone managed by bind have to be used. In later versions, unique names or in-view have to be used. Please visit ISC article [1], explaining proper configuration of views.

Even if it is possible to configure more slaves pointing to single file, it would result in unpredictable behaviour. Two views would race together and write into journals without proper synchronization. It is wrong configuration and cannot be fixed by software change. If we have some systems exporting it this way, it has to be fixed.

No error in bind package, closing.

1. https://kb.isc.org/docs/aa-00851

*** This bug has been marked as a duplicate of bug 1744081 ***