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:
Now that Bind has been rebased to 9.8.x it is possible to provide support for the Samba4-provided external DLZ module for AD-backed zones (currently the only DNS solution capable of secure DDNS in Samba4); unfortunately, this support is not enabled in current builds of Bind in RHEL6.

Version-Release number of selected component (if applicable):
9.8.2-0.10.rc1.el6_3.2

How reproducible:
Try to configure the Bind DLZ module in Samba4.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
External DLZ modules not supported.


Expected results:
Samba4-provided external DLZ module is correctly loaded.

Additional info:
Simply adding the "--with-dlopen=yes" option to the %configure part of the spec enabled such support; no adverse effects are expected for the other already shipped parts of Bind.
Note that bind-chroot support for the Samba4-provided module could require additional careful configuration.

After additional testing I suspect that the failures where probably due to other problems on the Samba4 side of things.

Furthermore Bind docs suggest that "--with-dlopen=yes" should be the default in versions >= 9.8.1

I'm going to test with the standard Bind package again asap and will report back.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

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-2014-1373.html