Bug 1401319

Summary: Using dnsmasq for DNS in NetworkManager fails after VPN reconnect
Product: [Fedora] Fedora Reporter: Rolf Fokkens <rolf>
Component: dnsmasqAssignee: Petr Menšík <pemensik>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 25CC: itamar, laine, thozza, veillard
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q4/010949.html
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-18 08:48:08 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:
Attachments:
Description Flags
Temporary workaround pending the upstream solution none

Description Rolf Fokkens 2016-12-04 18:17:04 UTC
Description of problem:
When setting dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf DNS resolving via the VPN works after the inital connection, but fails after reconnecting.

Version-Release number of selected component (if applicable):
dnsmasq-2.76-1.tgho2.fc25

How reproducible:
100%

Steps to Reproduce:
1. set dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf
2. make a VPN connection
3. disconnect the VPN
4. make a connection using the same VPN
5. note DNS resolving results in REFUSED when querying VPN hosts

Actual results:
REFUSED

Expected results:
DNS lookup

Additional info:

Comment 1 Rolf Fokkens 2016-12-04 18:50:26 UTC
It is a known issue upstream:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q4/010949.html

However:

http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2016q3/010831.html

It may take a while until it propagates to Fedora.

Comment 2 Rolf Fokkens 2016-12-04 18:55:17 UTC
Created attachment 1227942 [details]
Temporary workaround pending the upstream solution

Comment 3 Tomáš Hozza 2016-12-05 13:29:28 UTC
(In reply to Rolf Fokkens from comment #0)
> Description of problem:
> When setting dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf DNS
> resolving via the VPN works after the inital connection, but fails after
> reconnecting.
> 
> Version-Release number of selected component (if applicable):
> dnsmasq-2.76-1.tgho2.fc25

This build is not an official Fedora build. Please reproduce the issue with the latest official Fedora build and let us know.

Comment 4 Rolf Fokkens 2016-12-05 15:05:02 UTC
Sorry, I copy/pasted my (temporary) fixed release. The actual issue is in dnsmasq-2.76-1.fc25.

Comment 5 Tomáš Hozza 2016-12-05 15:33:38 UTC
(In reply to Rolf Fokkens from comment #4)
> Sorry, I copy/pasted my (temporary) fixed release. The actual issue is in
> dnsmasq-2.76-1.fc25.

Can you please retest with http://koji.fedoraproject.org/koji/buildinfo?buildID=821058 ?

Comment 6 Rolf Fokkens 2016-12-05 21:37:46 UTC
Yep, this one solves the issue!

Comment 7 Rolf Fokkens 2016-12-05 21:48:43 UTC
I see, the patch is the forementioned commit:

http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2675f2061525bc954be14988d64384b74aa7bf8b

Including a fix for the SIGSEGV I presume.

Comment 8 Fedora Admin XMLRPC Client 2017-02-16 21:25:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.