<html><head></head><body>For me, simply adding the lxc bridge IP address to DNS resolvers made me able to resolve *.lxd domains from the host machine.<br>
-- <br>
Matlink<br><br><div class="gmail_quote">Le 17 avril 2017 13:42:36 GMT+02:00, Simos Xenitellis <simos.lists@googlemail.com> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On Thu, Apr 13, 2017 at 10:49 PM, Norberto Bensa<br /><nbensa+lxcusers@gmail.com> wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Hello Simos,<br /><br /> 2017-04-13 10:44 GMT-03:00 Simos Xenitellis <simos.lists@googlemail.com>:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> I got stuck with this issue (Ubuntu Desktop with NetworkManager) and<br /> wrote about it at<br /> <a href="https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg07060.html">https://www.mail-archive.com/lxc-users@lists.linuxcontainers.org/msg07060.html</a><br /></blockquote><br /> For me, that doesn't work anymore with 17.04<br /><br /> I tried a lot of configuration options with dnsmasq, network-manager,<br /> and systemd-resolved with Ubuntu and Kubuntu (real hardware and<br /> virtualized with kvm).</blockquote><br /><br />If you installed additional packages or changed configuration options,<br />you might have changed something that alters the default behaviour.<br /><br />1. On Ubuntu Desktop, NetworkManager handles the networking configuration.<br />You should be able to do "ps aux | grep dnsmasq" and see at least one<br />"dnsmasq" process,<br />the one from NetworkManager.<br />For me, it is:<br />" 3653 ? S 0:00 /usr/sbin/dnsmasq --no-resolv<br />--keep-in-foreground --no-hosts --bind-interfaces<br />--pid-file=/var/run/NetworkManager/<a href="http://dnsmasq.pid">dnsmasq.pid</a><br />--listen-address=<a href="http://127.0.1.1">127.0.1.1</a> --cache-size=0 --conf-file=/dev/null<br />--proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq<br />--conf-dir=/etc/NetworkManager/dnsmasq.d"<br /><br />What is yours?<br /><br />2. NetworkManager uses dnsmasq as a caching nameserver, and it does so<br />by configuring /etc/resolv.conf with:<br /># Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)<br /># DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN<br />nameserver <a href="http://127.0.1.1">127.0.1.1</a><br /><br />Can you verify that you have exactly the same?<br /><br />3. Then, LXD should have it's own "dnsmasq" process (as a DHCP server<br />and caching nameserver).<br />This dnsmasq process binds on a specific private IP address, which you<br />can find with, for example,<br /><br />ifconfig lxdbr0<br /><br />In my case, it is <a href="http://10.0.125.1">10.0.125.1</a>. I have an LXD container called<br />"mycontainer", therefore I can run<br /><br />$ host mycontainer.lxd <a href="http://10.0.125.1">10.0.125.1</a><br />Using domain server:<br />Name: <a href="http://10.0.185.1">10.0.185.1</a><br />Address: <a href="http://10.0.185.1">10.0.185.1</a>#53<br />Aliases:<br /><br />mycontainer.lxd has address <a href="http://10.0.125.18">10.0.125.18</a><br />mycontainer.lxd has IPv6 address fd42:aacb:3658:4ca6:216:3e4f:fcd9:35e1<br />$ _<br /><br />Do you get such a result? If not, perhaps you have the wrong IP address.<br />Also, if you ran "lxd init" several times, you might have lingering<br />"dnsmasq" process<br />that bind on port 53 on lxdbr0. Would need to reboot here.<br /><br />If you can get up to this point, then the rest is really easy.<br /><br />Simos<br /><hr /><br />lxc-users mailing list<br />lxc-users@lists.linuxcontainers.org<br /><a href="http://lists.linuxcontainers.org/listinfo/lxc-users">http://lists.linuxcontainers.org/listinfo/lxc-users</a></pre></blockquote></div></body></html>