Bug 1382898 - NetworManager split DNS with dnsmasq broken after suspend
Summary: NetworManager split DNS with dnsmasq broken after suspend
Keywords:
Status: CLOSED DUPLICATE of bug 1373485
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-08 07:08 UTC by Aleksandar Kostadinov
Modified: 2016-10-08 08:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-08 08:33:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


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