It's arguably a dnsmasq/lxc problem that this can occur, but I think the
most relevant problem is Launchpad's setuplxc changing my dhclient
configuration.
I guess this was done so that the host could see launchpad.dev or
whatever.
But:
- changing basic networking of the host without warning peo
see bug 936817 for a broadly similar problem of it modifying the host
os.
--
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/956655
Title:
libvirt dnsmasq causes runaway chain reaction
ok, after discussion on irc, apparently it's launchpad's setuplxc that's
inserting the "conf:prepend domain-name-servers 10.0.3.1;" line.
I'm not sure if this problem could still be hit without it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
removing lxc has avoided the problem.
--
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/956655
Title:
libvirt dnsmasq causes runaway chain reaction
To manage notifications about this
mbp@joy% cat /var/run/nm-dns-dnsmasq.conf
server=10.0.3.1
server=192.168.178.1
server=10.0.3.1
server=192.168.178.1
I think this is an interaction between a few things that are themselves
reasonable:
- network-manager depends on dnsmasq, and makes it the default nameserver in
/etc/resolv.con