Bug 1382898

Summary:	NetworManager split DNS with dnsmasq broken after suspend
Product:	[Fedora] Fedora	Reporter:	Aleksandar Kostadinov <akostadi>
Component:	NetworkManager	Assignee:	Lubomir Rintel <lkundrak>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dcbw, fgiudici, lkundrak, psimerda, thaller
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-08 08:33:44 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:

Description Aleksandar Kostadinov 2016-10-08 07:08:07 UTC

Description of problem:
I am using NetworkManager with dnsmasq for split DNS when connected to VPN.

Since 2-3 days, after I some `dnf upgrade` the setup stopped working after machine is woken up from suspend.

That means, thing work as usual initially, I connect to the VPN, some domains are resolved by VPN DNS server and the rest through ISP name servers.

Then I suspend machine to RAM. Then I wake it up. Then I connect to VPN. But the domains that should resolve through VPN servers do not resolve.

If I kill dnsmasq that is run by NetworkManager, then situation recovers and everything works as expected. Before last update 2-3 days ago, things were alwais working fine.

Version-Release number of selected component (if applicable):
NetworkManager-1.2.4-2.fc24.x86_64
dnsmasq-2.76-1.fc24.x86_64

How reproducible:
always

Steps to Reproduce:
1. suspend while connected to VPN
2. wake-up laptop
3. connect to VPN
4. resolve VPN domain

Actual results:
name not found

Expected results:
resolved properly

Comment 1 Aleksandar Kostadinov 2016-10-08 07:08:37 UTC

FYI using NetworkManager-vpnc-1.2.2-1.fc24.x86_64

Comment 2 Thomas Haller 2016-10-08 08:33:44 UTC

it's a bug in dnsmasq

*** This bug has been marked as a duplicate of bug 1373485 ***