On Wed, 2015-12-16 at 10:45 -0500, Neal Becker wrote: > Tomasz Torcz wrote: > > > On Wed, Dec 16, 2015 at 09:33:18AM -0500, Neal Becker wrote: > > > P J P wrote: > > > > > > > > On Wednesday, 2 December 2015 6:33 PM, Neal Becker wrote: > > > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1287607 > > > > > > > > > > > > Thank you for filing the bug. > > > > > > > > > > > > > * howto prevent dnsmasq from starting (right now I'm just > > > > > manually > > > > > killing it for testing) > > > > > > > > # systemctl disable dnsmasq > > > > > > > > > > > > > > ps aux | grep dns > > > nobody 1056 0.0 0.0 57544 484 ? S Dec14 0:00 > > > /sbin/dnsmasq --conf-file=/var/lib/libvir > > > root 1058 0.0 0.0 57516 24 ? S Dec14 0:00 > > > /sbin/dnsmasq --conf-file=/var/lib/libvir > > > > Try > > systemctl status 1056 > > > > I guess it's started by libvirtd. > > > > Yes, and does it have to be stopped in order for local dns resolver > to > function? No, it doesn't. If you look at the config file for each instance you'll see interface=virbr0 (or something similar) except-interface=lo otherwise you'd never be able to run multiple VMs with different network setups. The libvirt dnsmasq instance should be binding to the interface that libvirt owns/manages and nothing else. Same thing for NetworkManager's "internet connection sharing" functionality with dnsmasq. But using NetworkManager's dns=dnsmasq config option *does* tell NM to spawn dnsmasq as a local caching nameserver listening on lo and that will conflict with unbound. Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
