I've been working on a workaround to dnsmasq being restarted all the time. Instead of overwriting the dnsmasq configuration and restarting dnsmasq; NM will not write any configuration file but start dnsmasq with --enable-dbus and push DNS changes using DBus. This can still mean there would be a small period of time where the DNS nameservers might not be up to date, but at least it should try to resolve with the old nameservers before the new ones are set.
This won't fix the extra host routes in the IPv6 routing table, but I think we should really consider that as a completely separate bug... (and IMO a cosmetic one, as I haven't been able to pinpoint any actual real-world effect of these extra routes to break anything). For testing on Precise as I start the SRU process for that fix (it needs to land in quantal first, and takes some time to be reviewed, then will be in proposed and need testing there...); I've already make NetworkManager and an accompanying patch to dnsmasq available in my ppa -- ppa:mathieu-tl/nm . Testing of NM with dnsmasq using the dbus method for updating nameservers would be much appreciated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1004775 Title: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup Status in “network-manager” package in Ubuntu: In Progress Status in “network-manager” source package in Precise: Triaged Status in “network-manager” source package in Quantal: In Progress Bug description: NetworkManager stops and starts dnsmasq very frequently (every few minutes). During the brief window that dnsmasq is restarting, hostname resolution doesn't work. dnsmasq is getting restarted frequently enough that I see brief hostname resolution errors in Chrome several times a day during normal web browsing. This is on Precise with network-manager 0.9.4.0-0ubuntu4 and dnsmasq- base 2.59-4. The frequent restarts seem to be triggered by IPv6 route advertisements on my network. (See log snippet below.) When NetworkManager gets a route advertisement, it reconfigures everything. In the case of dnsmasq, this means stopping dnsmasq, writing a new config file, and starting dnsmasq. NetworkManager should restart dnsmasq only if it its configuration changes. I'm attaching a snippet from /var/log/daemon.log on my system that demonstrates a restart. This is with debug logging configured in /etc/NetworkManager/NetworkManager.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1004775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
