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.
Bug 1061370 - no DNS from VPN when stop dnssec-triggerd
Summary: no DNS from VPN when stop dnssec-triggerd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: dnssec-trigger
Version: 7.0
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Tomáš Hozza
QA Contact: Juraj Marko
URL:
Whiteboard:
Depends On: 1063786
Blocks: 1063731
TreeView+ depends on / blocked
 
Reported: 2014-02-04 17:21 UTC by Juraj Marko
Modified: 2015-09-01 03:40 UTC (History)
5 users (show)

Fixed In Version: dnssec-trigger-0.11-21.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1063731 (view as bug list)
Environment:
Last Closed: 2014-06-13 09:23:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 Tomáš Hozza 2014-02-06 10:55:36 UTC
The more I think about the current solution, the more I don't think it's a good
approach to take care of restoring the resolv.conf by our own. Network Manager
has already all the necessary logic implemented and also solves some corner
cases (like adding the domain from FQDN hostname to the search domains in the
resolv.conf).

I'll create a new bug for NM to provide a way to make it reload its configuration
and adjust the existing settings (resolv.conf) if necessary.

As a workaround we could restart the NM on dnssec-trigger stop, but as a side
effect it would disconnect any existing VPN connections connected through NM.

Comment 12 Ludek Smid 2014-06-13 09:23:26 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.