At least two distinct issues have been discussed here. The original problem was that /etc/resolv.conf was not populated and the reason for this seems to have been that the symlink /etc/resolv.conf --> ../run/resolvconf/resolv.conf didn't get created. It would be nice to find out why that happened. Let's continue addressing that issue here (#1000244).
A second problem brought up by pdffs is that the upgrade to Precise breaks systems that had multiple nameserver addresses listed in resolv.conf, only the first of which can resolve private domain names. I have opened a new report, #1003842, to track this issue. pdffs: Please subscribe to #1003842 so we can continue the discussion there. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
