I think you may have misunderstood a bit. By "other local nameserver" I
meant also standalone dnsmasq, as opposed to the NetworkManager-
controlled dnsmasq process ("nm-dnsmasq"). If nm-dnsmasq listens at
127.0.0.2 then standalone dnsmasq can listen at 127.0.0.1 and on all
other IP addresses assigned to interfaces. Thus if #959037 is
implemented, you can use standalone dnsmasq for your purpose.
As to whether nm-dnsmasq will or will not be made more configurable,
I'll allow someone like Mathieu to speak to that.
--
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/1027166
Title:
dnsmasq config hard-coded into network manager
Status in “network-manager” package in Ubuntu:
Opinion
Bug description:
As indicated at http://www.stgraber.org/2012/02/24/dns-in-
ubuntu-12-04/#comment-39100 , Network Manager fires up dnsmasq using
hard-coded paramaters.
For those of us who want to use dnsmasq but need to tweak the
variables (for virtual machine use etc) , this isn't very helpful.
ideally, Network Manager should use a default file which can be
overridden.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1027166/+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
