<div dir="ltr">I actually don't have a separate dnsmasq instance running on the host. It's just the one that lxd manages. (DNS from inside the containers do work, but that's not my concern)<div><br></div><div>I realised forwarding queries to the lxd dnsmasq does work, ex:</div><div><br></div><div><div>dig @<a href="http://10.0.1.1">10.0.1.1</a> +short devop-tools.lxd</div><div>10.0.1.66</div><div><br></div><div>But just `dig +short devop-tools.lxd` doesn't. Which means the queries are not being forwarded to the lxds dnsmasq. I have added a nameserver entry to /etc/resolv.conf, but that hasn't helped.</div><div><br></div><div><div># Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)</div><div># DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN</div><div>nameserver 87.117.198.200</div><div>nameserver 87.117.237.100</div><div>nameserver 87.117.196.200</div><div>nameserver 10.0.1.1</div></div><div><br></div><div>Also, from what I've read /etc/resolv.conf this will get overridden on reboot, so this isn't a solution that will survive a reboot. Any ideas?</div><div><br></div><div> </div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 28, 2017 at 7:19 PM, Fajar A. Nugraha <span dir="ltr"><<a href="mailto:list@fajar.net" target="_blank">list@fajar.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Jun 28, 2017 at 6:34 PM, Adil Baig <span dir="ltr"><<a href="mailto:simplyadilb@gmail.com" target="_blank">simplyadilb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">This hasn't worked for me.<div><br></div><div><div>lxc network show lxdbr0 </div><div>description: ""</div><div>config:</div><div> dns.domain: lxd</div><div> dns.mode: managed</div><div> ipv4.address: <a href="http://10.0.1.1/24" target="_blank">10.0.1.1/24</a></div><div> ipv4.dhcp.ranges: 10.0.1.2-10.0.1.254</div><div> ipv4.nat: "true"</div><div> ipv6.address: none</div><div> raw.dnsmasq: conf-file=/home/ubuntu/stockop<wbr>edia-lxd-dnsmasq.conf</div><div></div></div></div></blockquote><div><br></div></span><div>why is raw.dsnmasq here?</div><div>while it might not be the cause of your non-working system, best to start with known-good configuration first.</div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I did steps 1.2 and 5. The rest were already in place (lxc version 2.14). I killed dnsmasq </div></div></blockquote><div><br></div></span><div>Again, the one doing resolving on the host. Not the one started by lxd to manage lxdbr0.</div><div><br></div><div>To be more accurate:</div><div>- lxd's dnsmasq should already provide DNS resolving for containers (e.g. "ping devop-tools.lxd" should work from inside any of your containers, as long as devop-tools is using DHCP).<br></div><div>- using dnsmasq as DNS resolver on the host as well would simplify the configuration. However it should work with any DNS server (e.g. bind) as long as you tell it to "forward all queries for .lxd domain to lxd's dnsmasq".</div><span class=""><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>and restarted lxd service (sudo service lxd restart) .</div><div><br></div></div></blockquote><div><br></div></span><div>That should not be necessary</div><span class=""><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div> ping devop-tools.lxd</div><div>ping: unknown host devop-tools.lxd</div></div></div><div class="m_5327336060473149768gmail-HOEnZb"><div class="m_5327336060473149768gmail-h5"><div class="gmail_extra"><br></div></div></div></blockquote><div><br></div></span><div>Does it work from another container? If not, you need to fix that first.</div><div><br></div><div>Does "dig" work when you tell it to use lxdbr0's IP as nameserver? e.g. "dig devop-tools.lxd @<a href="http://10.0.1.1" target="_blank">10.0.1.1</a>"</div><div><br></div><div>Do you get these entries when restarting the host's dnsmasq? If not, you probably edit the wrong file in step (5)</div><div># systemctl restart dnsmasq<br></div><div><div># systemctl status dnsmasq</div></div><div>...</div><div><div>Jun 28 20:43:29 ip-172-31-0-128 dnsmasq[92746]: using nameserver 10.0.3.1#53 for domain lxd</div></div><div><br></div><div>Does your host's /etc/resolv.conf now points to localhost? It should, since dnsmasq would make it so. If not, you need to fix that.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-- </div><div>Fajar</div></font></span></div></div></div>
<br>______________________________<wbr>_________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.<wbr>linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" rel="noreferrer" target="_blank">http://lists.linuxcontainers.<wbr>org/listinfo/lxc-users</a><br></blockquote></div><br></div>