[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from running, yet network-manager doesn't Conflict with their packages
Thomas Hood
959037 at bugs.launchpad.net
Tue Jun 12 10:13:24 UTC 2012
Alkis: Suppose your host, foo, has external IP address 10.1.2.3 and runs
a standalone nameserver which listens on eth0. Configure things such
that nm-dnsmasq on foo uses 10.1.2.3 as its upstream nameserver;
configure the standalone nameserver on foo not to listen on lo. If it's
dnsmasq, start it with --except-interface=lo. Does this do what you
want?
If so then this may be a very simple way to deal with #959037, at least
with respect to dnsmasq. Network-manager simply drops a file with
except-interface=lo
into /etc/dnsmasq.d/. NM can still use the local standalone dnsmasq via
the external network interface, the address of which it may receive from
the DHCP server, for example.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other DNS servers from running, yet
network-manager doesn't Conflict with their packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions
More information about the Ubuntu-server-bugs
mailing list