It seems at least standardized on Ubuntu Desktop.
Creating a /etc/NetworkManager/dnsmasq.d/lxd.conf file and restarting
network manager will do the trick, keeping the majority of developers
happy:
server=/lxd/10.0.4.1
(using the correct IP per lxd-bridge config of course)
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
