resolvconf does not reliable receive nameserver information from NetworkManager

Bug #1568787 reported by Dimitri John Ledkov on 2016-04-11
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
High
Unassigned
dnsmasq (Ubuntu)
High
Unassigned
network-manager (Ubuntu)
High
Unassigned

Bug Description

resolvconf does not reliable receive nameserver information from NetworkManager.

In the journal I see things like:

Apr 11 11:13:52 ottawa dnsmasq[3122]: setting upstream servers from DBus
Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver fe80::1#53
Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver 192.168.1.254#53
Apr 11 11:13:52 ottawa dbus[978]: [system] Rejected send message, 13 matched rules; type="method_return", sender=":1.99" (uid=0 pid=3122 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=1017 comm="/usr/sbin/NetworkManager --no-daemon ")

Apr 11 11:04:21 ottawa NetworkManager[1017]: <info> DNS: starting dnsmasq...
Apr 11 11:04:21 ottawa NetworkManager[1017]: <warn> dnsmasq not available on the bus, can't update servers.
Apr 11 11:04:21 ottawa NetworkManager[1017]: <error> [1460369061.825658] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name

Doing this via dbus seems really odd, but I suspect messages between NetworkManager and the dnsmasq it spawns should not be rejected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq-base 2.75-1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 11 11:17:34 2016
InstallationDate: Installed on 2016-01-26 (76 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125)
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)

Dimitri John Ledkov (xnox) wrote :
sourcepower (sourcepower) wrote :
Download full text (3.6 KiB)

- i can confirm the issue
- the DNS resolution was OK before i installed the last updates today
- how can i reproduce the issue:
-> 2 Network devices setup in Network Manager (LAN, not used; WLAN, used)
-> boot the system
-> WLAN will automatically connect to the WLAN network
-> /etc/resolv.conf (/run/resolvconf/resolv.conf) contains only "nameserver 127.0.1.1" as nameserver entry
- Workaround:
-> manually reconnect to WLAN network
-> /etc/resolv.conf (/run/resolvconf/resolv.conf) contains the configured nameserver
- i installed the following updates today

Start-Date: 2016-04-12 18:17:36
Commandline: apt-get upgrade
Requested-By: steven (1000)
Upgrade: libnm-glib4:amd64 (1.0.4-0ubuntu10, 1.1.93-0ubuntu2), libdevmapper1.02.1:amd64 (2:1.02.110-1ubuntu8, 2:1.02.110-1ubuntu9), liblvm2cmd2.02:amd64 (2.02.133-1ubuntu8, 2.02.133-1ubuntu9), dmsetup:amd64 (2:1.02.110-1ubuntu8, 2:1.02.110-1ubuntu9), language-pack-gnome-de:amd64 (1:16.04+20160403, 1:16.04+20160410), language-pack-gnome-en:amd64 (1:16.04+20160403, 1:16.04+20160410), irqbalance:amd64 (1.1.0-2, 1.1.0-2ubuntu1), python3-mako:amd64 (1.0.3+ds1-1, 1.0.3+ds1-1ubuntu1), appstream:amd64 (0.9.2-0ubuntu1, 0.9.3-1), libopencv-imgproc2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libopencv-objdetect2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libpulsedsp:amd64 (1:8.0-0ubuntu2, 1:8.0-0ubuntu3), pulseaudio:amd64 (1:8.0-0ubuntu2, 1:8.0-0ubuntu3), libopencv-video2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libdevmapper-event1.02.1:amd64 (2:1.02.110-1ubuntu8, 2:1.02.110-1ubuntu9), ubuntu-standard:amd64 (1.356, 1.357), ubuntu-desktop:amd64 (1.356, 1.357), dmeventd:amd64 (2:1.02.110-1ubuntu8, 2:1.02.110-1ubuntu9), libnm-glib-vpn1:amd64 (1.0.4-0ubuntu10, 1.1.93-0ubuntu2), lvm2:amd64 (2.02.133-1ubuntu8, 2.02.133-1ubuntu9), libnm0:amd64 (1.0.4-0ubuntu10, 1.1.93-0ubuntu2), alsa-utils:amd64 (1.1.0-0ubuntu2, 1.1.0-0ubuntu3), language-pack-de:amd64 (1:16.04+20160403, 1:16.04+20160410), language-pack-en:amd64 (1:16.04+20160403, 1:16.04+20160410), network-manager:amd64 (1.0.4-0ubuntu10, 1.1.93-0ubuntu2), gcc-6-base:amd64 (6-20160405-0ubuntu1, 6-20160405-0ubuntu2), gcc-6-base:i386 (6-20160405-0ubuntu1, 6-20160405-0ubuntu2), rsyslog:amd64 (8.16.0-1ubuntu2, 8.16.0-1ubuntu3), libopencv-flann2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libopencv-contrib2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libopencv-highgui2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libgcc1:amd64 (1:6-20160405-0ubuntu1, 1:6-20160405-0ubuntu2), libgcc1:i386 (1:6-20160405-0ubuntu1, 1:6-20160405-0ubuntu2), libnm-util2:amd64 (1.0.4-0ubuntu10, 1.1.93-0ubuntu2), libspectre1:amd64 (0.2.7-3ubuntu1, 0.2.7-3ubuntu2), ubuntu-minimal:amd64 (1.356, 1.357), libpulse0:amd64 (1:8.0-0ubuntu2, 1:8.0-0ubuntu3), liblvm2app2.2:amd64 (2.02.133-1ubuntu8, 2.02.133-1ubuntu9), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu2, 1:8.0-0ubuntu3), libopencv-calib3d2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), libopencv-legacy2.4v5:amd64 (2.4.9.1+dfsg-1.3ubuntu1, 2.4.9.1+dfsg-1.5ubuntu1), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu2, 1:8.0-0ubuntu3), l...

Read more...

Thomas Hood (jdthood) on 2016-04-12
description: updated
summary: - resolveconf does not reliable receive nameserver information from
- network manager
+ resolvconf does not reliable receive nameserver information from
+ NetworkManager
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
Changed in dnsmasq (Ubuntu):
status: New → Confirmed
Changed in network-manager (Ubuntu):
status: New → Confirmed
Tim Kuhlman (timkuhlman) wrote :

Another possible workaround I have used is to comment out the line "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf

Changed in dnsmasq (Ubuntu):
importance: Undecided → High
Changed in dbus (Ubuntu):
importance: Undecided → High
Changed in network-manager (Ubuntu):
importance: Undecided → High

I first experience this issue with nm version 1.8.2-1ubuntu1 in an - as of writing fully updated - 17.04.

Syslog will be attached, from that you can see that dnsmask gets the nameserver, networkmanager gets it too, but it doesn't make to resolv.conf, that will only have the stub resolver.

/etc/resolv.conf is a link ending in /run/resolvconf/resolv.conf.

Workaround is to manually add the nameserver to resolv conf and comment out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf which is really annoying on a laptop which you move around a lot.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers