FWIW on my laptop (16.10) DNS queries are working as I wish it (ie
"correctly"). With VPN disconnected all queries are going to the home router
(192.168.33.1), queries for eg amachine.csl are sent there and come back
NXDOMAIN.
With VPN connected, queries on .csl are going to the remote VPN server (as
requested for this domain suffix by the VPN server: no configuration on my
local machine here). Queries for anything else go to home router.
So dnsmasq logs this:
Nov 24 15:18:24 rukbat dnsmasq[6655]: query[A] amachine.csl from 127.0.0.1
Nov 24 15:18:24 rukbat dnsmasq[6655]: forwarded amachine.csl to 192.168.68.1
Nov 24 15:18:24 rukbat dnsmasq[6655]: reply amachine.csl is 192.168.68.44
HOWEVER, after disconnecting and then reconnecting VPN, despite dnsmasq having
noted this during the VPN connection set up:
Nov 24 15:24:51 rukbat dnsmasq[6655]: using nameserver
192.168.68.1#53 for domain csl
Now a request for say www.bbc.co.uk correctly goes through the home
router:
Nov 24 15:30:05 rukbat dnsmasq[6655]: query[A] www.bbc.co.uk from 127.0.0.1
Nov 24 15:30:05 rukbat dnsmasq[6655]: forwarded www.bbc.co.uk to 192.168.33.1
Nov 24 15:30:05 rukbat dnsmasq[6655]: reply www.bbc.co.uk is <CNAME>
Nov 24 15:30:05 rukbat dnsmasq[6655]: reply www.bbc.net.uk is 212.58.246.55
But a request for anothermachine.csl , only this is logged:
Nov 24 15:26:13 rukbat dnsmasq[6655]: query[A] anothermachine.csl
from 127.0.0.1
That's right, no "forwarded", no "reply" and the output of / dig
anothermachine.csl / has no answer:
;; QUESTION SECTION:
;anothermachine.csl. IN A
;; Query time: 0 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
In other words, dnsmasq doesn't even try. Looks like a bug in dnsmasq
(or a bug in Network Manager not instructing dnsmasq correctly).
** Tags added: dnsmasq
** Also affects: dnsmasq
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1644098
Title:
Network Manager + OpenVPN does not respond to DNS server change on
second connection attempt
Status in dnsmasq:
New
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Scenario:
Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I
only have the one computer to test with, the 16.10 is definitely relevant (I
did not have this problem on 16.04) but I can't tell if the upgrade is part of
it, (the upgrade may or may not be relevant).
Have "full time" wired or wireless connection (does not matter which used)
Part time OpenVPN connection set up via NetworkManager.
Steps to reproduce
1. Fresh boot
2. ping a device on the VPN network (eg amachine.remotelan ) Result:
"ping: amachine.remotelan: Name or service not known"
3. Connect to the VPN service via Network Manager.
4. ping amachine.remotelan - result:
PING amachine.remotelan (192.168.68.44) 56(84) bytes of data.
64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127
time=7.75 ms
5. Disconnect from the VPN service again.
ping result again "ping: amachine.remotelan: Name or service not known"
6. Reconnect to the VPN again, and ping again
Observed:
"ping: amachine.remotelan: Name or service not known"
However "ping 192.168.68.44" responds successfully as expected
Expected:
PING ... 192.168.... 64 bytes from .. etc to the ping by name
---------------
Further info I'm going to add in a subsequent comment. (just annotating
syslog right now!)
To manage notifications about this bug go to:
https://bugs.launchpad.net/dnsmasq/+bug/1644098/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
