Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When a new zone appears or disappears, a reload of named should be forced from the plugin, so that new zone becomes usable without requiring an explicitly reload action from the admin.
Version-Release number of selected component (if applicable):
bind-dyndb-ldap-0.2.0-3.20110426T0344z.el6.x86_64
How reproducible:
You can test it for example in IPA with DNS-support.
Steps to Reproduce:
1. ipa dnszone-add NEWZONE
2. dig NEWZONE
3.
Actual results:
NEWZONE data are not resolvable until Bind is restarted on the master.
Expected results:
Plugin should reload Bind so that the new zone can be resolved
Additional info:
There is an upstream bind-dyndb-ldap ticket:
https://fedorahosted.org/bind-dyndb-ldap/ticket/31
Verified against ipa-server.x86_64 0:2.1.4-101.20111102T0110zgitc10db54.el6
11-4-2011
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [ LOG ] :: ipa-dns-07: create a new zone
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Zone name: newzone
Authoritative nameserver: ipaqa64vmh.testrelm.
Administrator e-mail address: ipaqar.redhat.com.
SOA serial: 2010010701
SOA refresh: 303
SOA retry: 101
SOA expire: 1202
SOA minimum: 33
SOA time to live: 55
Active zone: TRUE
Dynamic update: FALSE
:: [ PASS ] :: Checking to ensure that ipa thinks that it can create a zone
Shutting down dirsrv:
PKI-IPA...[ OK ]
TESTRELM...[ OK ]
Starting dirsrv:
PKI-IPA...[ OK ]
TESTRELM...[ OK ]
Stopping Kerberos 5 KDC: [ OK ]
Starting Kerberos 5 KDC: [ OK ]
Shutting down ipa_kpasswd: [ OK ]
Starting ipa_kpasswd: [ OK ]
Stopping named: .[ OK ]
Starting named: [ OK ]
Stopping httpd: [ OK ]
Starting httpd: [Wed Nov 02 17:57:16 2011] [warn] worker ajp://localhost:9447/ already used by another worker
[Wed Nov 02 17:57:16 2011] [warn] worker ajp://localhost:9447/ already used by another worker
[ OK ]
Stopping pki-ca: [ OK ]
Starting pki-ca: [ OK ]
Restarting Directory Service
Restarting KDC Service
Restarting KPASSWD Service
Restarting DNS Service
Restarting HTTP Service
Restarting CA Service
:: [ PASS ] :: Restarting IPA server
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1715.html