How do I get the default Network Manager plus dnsmasq-base setup back again?

[Chris Green]

On Sun, Jan 06, 2013 at 04:55:10PM -0500, Tom H wrote:
[snip long list of tests etc.]
> 
> I purged dnsmasq and the situation returned to the previous
> "integrated/builtin" behavior.
> 
> Are you sure that you have "dns=dnsmasq" in
> "/etc/NetworkManager/NetworkManager.conf"?
> 
Here's my /etc/NetworkManager/NetworkManager.conf :-

    [main]
    plugins=ifupdown,keyfile
    dns=dnsmasq

    [ifupdown]
    managed=false

> What's the output of "ls /etc/dbus-1/system.d/"?
> 
This:-

    root at chris:/var/log# ls /etc/dbus-1/system.d/
    ConsoleKit.conf                          org.debian.apt.conf
    Mountall.Server.conf                     org.freedesktop.Accounts.conf
    Upstart.conf                             org.freedesktop.ColorManager.conf
    avahi-dbus.conf                          org.freedesktop.DisplayManager.conf
    bluetooth.conf                           org.freedesktop.ModemManager.conf
    com.hp.hplip.conf                        org.freedesktop.NetworkManager.conf
    com.redhat.NewPrinterNotification.conf   org.freedesktop.PackageKit-aptd.conf
    com.redhat.PrinterDriversInstaller.conf  org.freedesktop.PolicyKit1.conf
    com.ubuntu.DeviceDriver.conf             org.freedesktop.RealtimeKit1.conf
    com.ubuntu.LanguageSelector.conf         org.freedesktop.SystemToolsBackends.conf
    com.ubuntu.SoftwareCenter.conf           org.freedesktop.UDisks.conf
    com.ubuntu.SoftwareProperties.conf       org.freedesktop.UDisks2.conf
    com.ubuntu.USBCreator.conf               org.freedesktop.UPower.conf
    dnsmasq.conf                             org.freedesktop.colord-sane.conf
    kerneloops.dbus                          org.kde.auth.conf
    nm-avahi-autoipd.conf                    org.kde.kcontrol.k3bsetup.conf
    nm-dhcp-client.conf                      org.kde.kcontrol.kcmremotewidgets.conf
    nm-dispatcher.conf                       org.kubuntu.qaptworker.conf
    nm-pptp-service.conf                     pulseaudio-system.conf
    org.blueman.Mechanism.conf               wpa_supplicant.conf
    org.debian.AptXapianIndex.conf

> This is the log of the last reboot:
> 
> root at dnsmasqtest:~# grep dnsmasq /var/log/syslog
> Jan  6 21:26:49 dnsmasqtest NetworkManager[672]: <info> DNS: loaded
> plugin dnsmasq
> Jan  6 21:27:09 dnsmasqtest NetworkManager[672]: <info> DNS: starting dnsmasq...
> Jan  6 21:27:09 dnsmasqtest NetworkManager[672]: <error>
> [1357507629.91780] [nm-dns-dnsmasq.c:390] update(): dnsmasq not
> available on the bus, can't update servers.
> Jan  6 21:27:09 dnsmasqtest NetworkManager[672]: <error>
> [1357507629.91875] [nm-dns-dnsmasq.c:392] update(): dnsmasq owner not
> found on bus: Could not get owner of name
> 'org.freedesktop.NetworkManager.dnsmasq': no such name
> Jan  6 21:27:09 dnsmasqtest NetworkManager[672]: <warn> DNS: plugin
> dnsmasq update failed
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: started, version 2.63rc6
> cache disabled
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: compile time options: IPv6
> GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: DBus support enabled:
> connected to system bus
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: warning: no upstream servers
> configured
> Jan  6 21:27:09 dnsmasqtest NetworkManager[672]: <warn> dnsmasq
> appeared on DBus: :1.9
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: setting upstream servers from DBus
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: using nameserver 8.8.4.4#53
> Jan  6 21:27:09 dnsmasqtest dnsmasq[902]: using nameserver 8.8.8.8#53
> root at dnsmasqtest:~#
> 
> Amazingly, NM gets the dns servers from "/var/run/dnsmasq/resolv.conf"
> when dnsmasq is installed and "dns=dnsmasq" is commented out in
> "/etc/NetworkManager/NetworkManager.conf"! (I deleted syslog before my
> last reboot so I can't post those logs.)
> 
All I get to see in /var/log/syslog (about dnsmasq) is:-

    Jan  9 14:51:03 test NetworkManager[872]: <info> DNS: loaded plugin dnsmasq

Network Manager continues to report all sorts of other things happening but not a thing
about dnsmasq.  It's like dnsmasq simply hangs when it's loaded.

-- 
Chris Green