That's not meant to work from the host, but for machines using the
dnsmasq server, so only between containers.
We can't easily configure the host to use our dnsmasq because there is
no standardized way to do so, the lxd dnsmasq only starts running when
LXD starts and LXD doesn't start on boot.
root@trusty:~# ping blah.lxd
PING blah.lxd (10.212.54.7) 56(84) bytes of data.
64 bytes from blah.lxd (10.212.54.7): icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from blah.lxd (10.212.54.7): icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from blah.lxd (10.212.54.7): icmp_seq=3 ttl=64 time=0.049 ms
^C
--- blah.lxd ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.049/0.053/0.062/0.010 ms
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571967
Title:
.lxd domain resolution not working after standard installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1571967/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
