Tested on a cloud instance which doesn't have a local dnsmasq, it ended up with the following config:
$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.88.0.1 nameserver 10.55.60.1 search vpn.ubuntone.info canonistack Removing the --strict-order seems to solve the problem every single time consistently. -- 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/libvirt/+bug/1205086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
