Please don't enable the NetworkManager-controlled dnsmasq by default

[Ryan Farmer]

In Ubuntu's default configuration, NetworkManager spawns a copy of dnsmasq, which breaks DNS lookups for me. It has done this since Ubuntu 12.04, when this was made the default. I've just been following the workaround that has worked for other people of disabling dnsmasq in /etc/NetworkManager/NetworkManager.conf.

There have been multiple bug reports about the various problems of this configuration, but it remains the default configuration in 12.10, and breaks my DNS lookups there, as well.

Someone mentioned I should file a bug. So, why not? It'll just be ignored like they always are, but fine. You got it!

[Thomas Hood (jdthood)]

There are really two issues here. One is that nm-dnsmasq isn't working properly for you. The second is that you'd like it not to be enabled by default.

Let's consider this report (bug #1086693) to be your request that nm-dnsmasq not be enabled by default.

Please take a look at the reports that have already been filed against the dnsmasq package, especially bug #1003842. If you feel that your bug is different, file a new report against dnsmasq. These reports are not ignored!

[Launchpad Janitor (janitor)]

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

[Nick Craig-Wood (nick-craig-wood)]

I think failing intermittently is the problem rather than the one in bug #1003842

Having disabled dnsmasq my networking is now reliable, rather than being intermittent. Sometimes public names would resolve and sometimes they wouldn't.

[Ryan Farmer (ryanfarmer-t)]

It still doesn't work right in 13.04. Why should people installing Ubuntu know to edit a configuration file that their account doesn't even own before their networking will work?