*** This bug is a duplicate of bug 1639776 ***

** This bug is no longer a duplicate of bug 1675519
   Network Manager w/ dnsmasq Dies when VPN-ing
** This bug has been marked a duplicate of bug 1639776
   dnsmasq fails to send queries out after suspend disconnects the interface

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.

  Network manager does not resolve dns names

Status in network-manager package in Ubuntu:

Bug description:
  NM seems completely broken in 16.10.

  I use NM, wifi and several VPN connections.

  Expected behaviour:

  1. Connect NM to default wlan -> name resolution works without interuption 
and permanently
  2. Connection to Cisco Anyconnect (via openconnect) -> DNS servers sent via 
DHCP should be added to the resolver list, name resolution should work in 
destination network, routes adjusted accordingly
  3. Connect NM to foreign network (WPA2) -> DNS resolution sent via DHCP 
should be taken as default

  Current behaviour:

  NM starts dnsmasq by default (I commented the start line to fix
  issues). DNS resolution stops after some minutes.

  Removing dnsmasq fron NetworkManager.conf (as I did) allows for name
  resolution except for web browsers (neither Firefox nor Chromium use
  the systemd.resolver).

  5 minutes of inactivity on the network suffice for the name resolution
  to stop working. Have to reestablish network connection (sudo
  resolveconf -u does not work).

  This violates expectation 1

  NM connects via openconnect. In the settings I added additional DNS
  servers and domain searches. They are ignored by dnsmasq. Name
  resolution does not work.

  *Worksaround* -> enter IP-addresses in /etc/hosts.

  dig @server-ip returns the correct IP address for target services but
  Firefox and Chromium do not utilize these services. dnsmasq does not
  return the correct address.

  This violates expectation 2

  Entering a foreign but known network, DNS resolution stops after a
  while (5 minutes inactivity suffice).


  a. DNS resolution using VPN connections does not work (I use openvpn, 
openconnect and pptp).
  b. dnsmasq does not resolve dns names correctly in wlan situations
  c. dnsmasq conflicts with systemd.resolver
  d. Firefox and Chromium ignore systemd.resolver
  e. removing dnsmasq from NetworkManager.conf releaves the issue a little 
(resolution drop-outs do not occur so frequently)

  Comparison to plain Debian demonstrated that Debian does not start
  dnsmasq. This led to the elimination of my dns=dnsmaq line in

  Comparison to Raspian demonstrated that Raspian uses wpa_supplicant to
  control dns name resolution. I have not tried this setup in Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 23 11:28:21 2017
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-27 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
   default via dev wlp4s0  proto static  metric 600 dev wlp4s0  proto kernel  scope link  src  metric 600 dev wlp4s0  scope link  metric 1000 dev vmnet8  proto kernel  scope link  src dev vmnet1  proto kernel  scope link  src
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
   DEVICE  TYPE      STATE      DBUS-PATH                                  
CONNECTION  CON-UUID                              CON-PATH                      
   wlp4s0  wifi      connected  /org/freedesktop/NetworkManager/Devices/2  
rsb_hs      7a8389dc-afd3-444b-a106-1974e9e74dff  
   vmnet1  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
       --                                    --                                 
   vmnet8  ethernet  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
       --                                    --                                 
   lo      loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/3  --   
       --                                    --
   running  1.2.6    connected  started  full          enabled     enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to