Public bug reported: In my setup I have a non-recursive name server that gets pushed as part of a vpn setup. This name server only resolves addresses that are part of the vpn. It gets pushed to the top of the resolv.conf file by /etc/openvpn/update-resolv-conf.
Since the dnsmasq instance set up by lxc-net is started with --strict- order, containers fail to resolve addresses completely, since they hit the first name server and it does not resolve any addresses outside of the vpn. Removing the --strict-order option in /etc/init/lxc-net.conf and restarting makes name resolution in the containers work. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205086 Title: lxc-net dnsmasq --strict-order breaks dns for lxc non-recursive nameserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1205086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs