@jdthood: - /etc/resolv.conf did not exist in any form on a clean install, prior to dpkg-reconfiguring resolvconf - DNS resolution worked with the following caveats: - search domains offered via DHCP were not honored - random order nameserver querying and caching by dnsmasq results in persistently broken queries if not all nameservers have all records
To explain the latter - we use a couple of internal nameservers which return internal domains, and a fallback external nameserver, which obviously doesn't carry the internal domains. Because dnsmasq queries random servers, if the external is hit first, all subsequent queries for that hostname will fail due to caching. Obviously we can work around this by disabling the external resolver (though there are other scenarios where server preference matters), and the lack of search domains renders all our intranet documentation broken. -- 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
