Short-term fix is to `dpkg-reconfigure resolvconf` and enable the option to 'Prepare /etc/resolv.conf for dynamic updates' or whatever it says. Then, `resolvconf --enable-updates` (the latter may not be needed).
Also, your search domain won't work if you're using the dnsmasq method in networkmanager (and if you've got fallback resolvers in addition to one that provides your internal domain, you'll also get random name resolution failures for the internal domain because dnsmasq picks random resolvers). Another fine balls-up - seriously, name resolution is a core requirement, how does this poorly tested new stuff keep ending up in LTS releases? Seriously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: Network Manager does not populate resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
