Looking more through comments in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1003842, it appears to me that the most uncontraversial fix, rather than removing --strict-order in lxc's dnsmasq, would be for dnsmasq on your host to have something like:
server=/vpn.ubuntuone.info/10.88.0.1 and not have 10.88.0.1 in your resolv.conf at all. Mind you I do hate suggesting changes to otherwise-working setups to work around what can appear to be problems elsewhere. But going by http://www.zoneedit.com/doc/rfc/rfc2182.txt that appears to be the "correct" thing to do. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in 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-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
