Public bug reported:
When libvirt configures / starts up dnsmasq on the host, it does not
pass --no-hosts, resulting in it reading in the /etc/hosts file from the
host.
The default ubuntu setup will have the host's hostname in /etc/hosts
under 127.0.1.1. Since libvirt's dnsmasq is reading this file, anything
querying that dnsmasq instance will resolve the host's hostname out of
/etc/hosts.
The result of this is any VM running on the host will resolve the host's
hostname as 127.0.1.1. For example, if the host's hostname is BoxA, any
VM running on the host will resolve BoxA to 127.0.1.1, which is not
BoxA's actual address.
Would recommend passing --no-hosts to dnsmasq when libvirt starts it up.
If a user wants hardcoded hosts for their libvirt network, they can add
them to /var/lib/libvirt/dnsmasq/default.addnhosts . If this is an
acceptable solution, I'd be happy to write the patch up.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd
behaviour for the domain
+ libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in odd
resolution behaviour on the VM
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1326536
Title:
libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in
odd resolution behaviour on the VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1326536/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
