On Mon, Jul 23, 2012 at 09:00:59PM -, Thomas Hood said:
> 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 standalo
On Sat, Jul 21, 2012 at 09:10:44PM -, 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 includ
It is set to only listen on 127.0.0.1 but I want to set it to listen on
another interface/address, as I have a virtual machine which is trying
to send DNS packets to that interface.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-
Public bug reported:
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 helpf
4 matches
Mail list logo
