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 using NetworkManager with dns=unbound, NM expects dnssec-trigger to update unbound configuration based on network events. Current dnssec-trigger version is too old to have that capability so unbound rebase seems a good thing to do at this point.

Version-Release number of selected component (if applicable):
dnssec-trigger-0.11-21.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. setup NM with dns=unbound (also enable unbound and dnssec-triggerd services)
2. change network configuration
3.

Actual results:
NetworkManager[18412]: <warn>  could not spawn process '/usr/libexec/dnssec-trigger-script --async --update': Failed to execute child process "/usr/libexec/dnssec-trigger-script" (No such file or directory)
NetworkManager[18412]: <warn>  DNS: plugin unbound update failed

Expected results:
dnssec updates unbound configuration

Additional info:

While rebasing dnssec-trigger is definitely a good idea, it is not yet in a shape in which we can put in into RHEL.

The version available in RHEL-7 does not need the NetworkManager "unbound" DNS module. It will function in autonomous way. This means you don't need to set "dns=" in NM configuration at all, or you can set it to "dns=none". NM is usually rebased to the latest Upstream version, therefore its code is ahead of what is available in dhssec-trigger.

For more information about how to set-up NM in RHEL-7, please see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/sec-Securing_DNS_Traffic_with_DNSSEC.html

*** Bug 1110136 has been marked as a duplicate of this bug. ***

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.