> Finally, on my host I get: > root@srv-Ub1404:~# ps -ef | grep dnsmasq > lxc-dns+ 11309 1 0 Jan15 ? 00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
so your dnsmasq is listening on 10.0.3.1 but serving 10.0.1.2..10.0.1.254. Is that by design, or should it be serving 10.0.3.2..10.0.3.254?
Since you're using a non-standard setup anyway, you should be able to get dns in your containers by putting
nameserver 10.0.3.1
into /etc/resolv.conf, or else
nameserver 8.8.8.8
> Finally, on my host I get: /run/lxc/ dnsmasq. pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.1.2,10.0.1.254 --dhcp- lease-max= 253 --dhcp-no-override --except- interface= lo --interface=lxcbr0 --dhcp- leasefile= /var/lib/ misc/dnsmasq. lxcbr0. leases --dhcp- authoritative
> root@srv-Ub1404:~# ps -ef | grep dnsmasq
> lxc-dns+ 11309 1 0 Jan15 ? 00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=
so your dnsmasq is listening on 10.0.3.1 but serving 10.0.1. 2..10.0. 1.254. Is that by design, or should it be serving 10.0.3. 2..10.0. 3.254?
Since you're using a non-standard setup anyway, you should be able to
get dns in your containers by putting
nameserver 10.0.3.1
into /etc/resolv.conf, or else
nameserver 8.8.8.8