Please allow disabling of the NM-controlled dnsmasq via the GUI

[Pas]

There is already a patch, submitted to the networkmanager-list ( https://mail.gnome.org/archives/networkmanager-list/2012-June/msg00011.html ) on Jun 1, so this is just a tracking bug, however, hopefully it at least shows that there's some interest in customizing the dnsmasq command line that NetworkManager uses to launch the caching resolver.

[Thomas Hood (jdthood)]

Instead of letting the user custom-configure NM-controlled dnsmasq, what if we cascade traditional standalone dnsmasq (which can be custom configured) to NM-controlled dnsmasq (which can't be) --- the former forwarding to the latter? Would this address the libvirt-network use case mentioned in the upstream report?

(At present, standalone dnsmasq can't be started when NetworkManager-controlled dnsmasq is running. This is bug #959037. However, in comment #67 of that report I describe how to get both dnsmasq instances running in cascade.)

[Pas (pasthelod)]

So after switching to GNOME3 the Network Manager GUI works again (or maybe a restart could've achieved the same for Unity), where setting up custom DNS servers is an option, and it gets correctly transliterated into /run/nm-dns-dnsmasq.conf.

Of course setting up a chain of resolvers seems a bit overkill, so maybe providing an option for disabling the NM-controlled dnsmasq would be the best (and the user could then punch in 127.0.0.1 via the GUI, or by setting up a system-connection config file in /etc/NetworkManager/).

[Thomas Hood (jdthood)]

It would be nice to be able to add options to the nm-dnsmasq command line for debugging purposes, at least.

[Thomas Hood (jdthood)]

> so maybe providing an option for disabling the NM-controlled dnsmasq would be the best

Retitling.