Pdf in #7: > Well, commenting the line is not too bad, except that > other resolvconf bugs mean that doing so actually > results in no name resolution at all
Pdf in #11: > I mentioned that resolv.conf was missing in #1000244, > and since it wasn't being populated correctly, so if it's > not being populated, and you disable dnsmasq, that > would result in no resolution... We aren't getting duplicates of #1000244 so it's probably not a frequently occurring problem. If resolvconf were systematically failing to create the resolv.conf symlink we'd be getting hundreds of reports about it. Based on what we know now it's most probable that #1000244 was a result of some sort of administrator error. The version of resolvconf that was included in Precise wasn't perfect but the bugs were fairly minor and the known ones have since been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: Precise NM with "dns=dnsmasq" breaks systems with non-equivalent upstream nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
