On Sat, Jul 21, 2012 at 09:10:44PM -0000, Thomas Hood said: > Look at bug #959037, e.g., comment #88. It is proposed there that nm- > dnsmasq listen on 127.0.0.2 instead of 127.0.0.1 so that nm-dnsmasq > doesn't interfere with other local nameservers that want to listen on > all interfaces including lo. If that is implemented then your specific > problem will also be solved. You are invited to describe your own needs > in bug #959037.
I am not trying to use other name servers, I do just want to use dnsmasq. The issue is that I want it to listen on all IPs that are active. What you describe under "longer term" in #959037/#88 appears to suggest this will be the case. > I don't think that nm-dnsmasq will be changed to allow arbitrary > customization. I can imagine certain dnsmasq options being exposed to > the user but in each case this will have to be requested and argued for. I am interested in why not? I understand that you want to provide a set of defaults by why hard code them rather than use a config file which can be overridden by a clueful user if they want to? N -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027166 Title: dnsmasq config hard-coded into network manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1027166/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
