I agree with the reassignment - it is a network-manager issue. Here is the information requested, plus some more. Please ask for more if needed, and I you wish me to run some tests, tell me.
The system affected was originally created by Kubuntu 12:04 installer - to the best of my knowledge I have not deviated from what is default in that distribution with regards to network manager and dns configuration. The only vaguely relevant change I have made is to configure an IPSec based VPN. I included a piece of the syslog, mainly because it is a little different from the one in the original report: Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> (eth0): DHCPv4 state changed nbi -> preinit Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: Listening on LPF/eth0/5c:26:0a:75:8f:b0 Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: Sending on LPF/eth0/5c:26:0a:75:8f:b0 Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: Sending on Socket/fallback Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPREQUEST of 10.10.129.108 on eth0 to 255.255.255.255 port 67 Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPOFFER of 10.10.129.108 from 10.10.129.2 Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: DHCPACK of 10.10.129.108 from 10.10.129.2 Sep 21 07:57:15 pcn-Latitude-E6520 dhclient: bound to 10.10.129.108 -- renewal in 3421 seconds. Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> (eth0): DHCPv4 state changed preinit -> bound Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> address 10.10.129.108 Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> prefix 24 (255.255.255.0) Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> gateway 10.10.129.1 Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> nameserver '192.168.253.250' Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> nameserver '192.168.253.251' Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> domain name 'intern.it-huset.dk' Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Sep 21 07:57:15 pcn-Latitude-E6520 NetworkManager[1271]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started... Sep 21 07:57:15 pcn-Latitude-E6520 charon: 02[KNL] 10.10.129.108 appeared on eth0 Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Activating service name='org.freedesktop.ColorManager' (using servicehelper) Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Successfully activated service 'org.freedesktop.ColorManager' Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Activating service name='org.freedesktop.colord-sane' (using servicehelper) Sep 21 07:57:15 pcn-Latitude-E6520 dbus[1101]: [system] Successfully activated service 'org.freedesktop.colord-sane' Sep 21 07:57:15 pcn-Latitude-E6520 charon: 02[KNL] fe80::5e26:aff:fe75:8fb0 appeared on eth0 Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> (eth0): device state change: ip-config -> activated (reason 'none') [70 100 0] Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> DNS: starting dnsmasq... Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <error> [1348207036.182474] [nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update servers. Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <error> [1348207036.182491] [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 Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <warn> DNS: plugin dnsmasq update failed Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> ((null)): writing resolv.conf to /sbin/resolvconf Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: started, version 2.63rc6 cache disabled Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: DBus support enabled: connected to system bus Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: warning: no upstream servers configured Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS. Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> Activation (eth0) successful, device activated. Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete. Sep 21 07:57:16 pcn-Latitude-E6520 dbus[1101]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <warn> dnsmasq appeared on DBus: :1.15 Sep 21 07:57:16 pcn-Latitude-E6520 NetworkManager[1271]: <info> ((null)): writing resolv.conf to /sbin/resolvconf Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: setting upstream servers from DBus Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: using nameserver 192.168.253.251#53 Sep 21 07:57:16 pcn-Latitude-E6520 dnsmasq[1595]: using nameserver 192.168.253.250#53 As you can see, it is a kind of timing issue: At a certain point in time the network-manager needs the dnsmasq on the bus but cannot find it, therefore it fails to complete the configuration; a little later (actually within the same second) it discovers that the dnsmasq pops up. And now to your questions: The dnsmasq package is not installed, but the dnsmasq-base is, version 2.63-1ubuntu1. The only dnsmasq-releated configuration file present is /etc/dnsmasq.d /network-manager, with the content # Tell any system-wide dnsmasq instance to make sure to bind to interfaces # instead of listening on 0.0.0.0 # WARNING: changes to this file will get lost if network-manager is removed. bind-interfaces The /etc/resolv.conf file is not updated at all, so the content is probably not of any relevance - it is whatever it was the last time I edited it. Right now it is: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.253.251 nameserver 192.168.253.250 search intern.it-huset.dk - the two servers mentioned are nameservers on our house internal network. In normal operation (before I upgraded to 12:10 Beta 1) it says "nameserver 127.0.0.1". In /run/resolvconf/interface I find one file, NetworkManager with the content domain intern.it-huset.dk search intern.it-huset.dk nameserver 127.0.1.1 And finally, no, no other nameserver installed, specifically not bind. Best regards Peder Chr. Nørgaard, M.Sc. Senior SW Developer www.actua.dk - Software that transforms the business of Energy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: "dnsmasq not available on the bus" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs