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.

Bug 1061370

Summary:	no DNS from VPN when stop dnssec-triggerd
Product:	Red Hat Enterprise Linux 7	Reporter:	Juraj Marko <jmarko>
Component:	dnssec-trigger	Assignee:	Tomáš Hozza <thozza>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Juraj Marko <jmarko>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	hhorak, jmarko, jscotka, nlevinki, thozza
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	dnssec-trigger-0.11-21.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1063731 (view as bug list)		Environment:
Last Closed:	2014-06-13 09:23:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1063786
Bug Blocks:	1063731

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.