Comment 0 for bug 1568787

resolveconf does not reliable receive nameserver information from network manager.

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)