This bug is still present in ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326536
Title:
libvirt's dnsmasq setup will read /etc/hosts on the host, resulting in
odd resolution
Right, my hack is almost the same as --no-hosts, it just doesn't require
patching libvirt.
Do you need that entry in your /etc/hosts? If you have a real DNS name,
you might not need it at all. If not, but you have a static IP address,
you could use that in the hosts file instead of 127.0.1.1.
--
Thanks Nathan to share you workaround as well, but IMHO it is "just as
good" as the --no-hosts flag. In that I mean while it prevent the reply
of 127.0.1.1 for the Host it also stops any other entry in Hosts to be
used (which users might want or even already rely on).
Darragh, Jason and Serge
I had the same problem (on 16.04.02) and came up with a rather dirty,
but quick and effective workaround.
Simply remove the libvirt-dnsmasq user's ability to read /etc/hosts:
sudo setfacl -m user:libvirt-dnsmasq:--- /etc/hosts
The libvirt dnsmasq instances will syslog a complaint when they
Did some more testing (found how to adjust libvirts dnsmasq.conf and
restart it to pick up conf changes):
To test, get the dnsmasq pid using the vagrant-libvirt.conf config and check
the environment set for the process with:
sudo cat /proc/2586/environ
VIR_BRIDGE_NAME=virbr0
After killing the
Never mind, I took some time to patch libvirt to see if it would have
any effect. Appears to only apply to the records dnsmasq receives the
DNS queries it makes, doesn't ignore any addresses read in from
/etc/hosts.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Perhaps a change could be added to ignore 127.0.0.1 and 127.0.1.1
addresses returned by default?
Dnsmasq supports such an option, though it would need to be added to
libvirt as it regerates the dnsmasq conf file used each time a network
is started.
Add following by default to dnsmasq.conf
Hi Stéphane,
assigned this to you just to get your input, as I imagine you have a
perfect solution right offhand.
On my servers, /etc/hosts lists the hostname as public ip address, and
there is no problem. On my laptops with network-manager, when I start
a container and 'ping laptop-name', it
Hi Stéphane,
assigned this to you just to get your input, as I imagine you have a
perfect solution right offhand.
On my servers, /etc/hosts lists the hostname as public ip address, and
there is no problem. On my laptops with network-manager, when I start
a container and 'ping laptop-name', it
Thanks for submitting this bug. Tested and reproduced the same, and
agreed this should be fixed. Looks like this should be pretty simple to
fix at src/network/bridge_driver.c:networkBuildDhcpDaemonCommandLine().
The patch however should also go upstream for feedback there.
Thanks for offering
I created a small patch to place the no-hosts option in the config file
which libvirt creates. (I figured that was more appropriate than setting
the flag, since all other options are set in those config files by
libvirt).
Unfortunately I'm unfamiliar with libvirt's testing suite, and couldn't
The attachment Applies to a7b0040 on git://libvirt.org/libvirt.git
seems to be a patch. If it isn't, please remove the patch flag from
the attachment, remove the patch tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
12 matches
Mail list logo
