> Speeding up DNS search did not require adding resolvconf > to ubuntu-minimal. > Instead, enabling dhclient's option to always prepend > 127.0.0.1 to /etc/resolv.conf does the trick quite nicely.
If you only have one interface configurer (e.g., dhclient) then there is no problem having that configurer control /etc/resolv.conf. If you have only one interface configurer and you always have a caching nameserver then /etc/resolv.conf can statically contain 127.0.0.1 and the interface configurer can convey its nameserver addresses to the caching nameserver. (If the caching nameserver is dnsmasq, one way to convey the information is to write the addresses to /etc/resolv.conf and dnsmasq will read them from there.) Resolvconf doesn't offer any benefits under these circumstances. (Nor should it bring disbenefits.) Resolvconf is only really beneficial when the system has multiple interface configurers. Then it, or something like it, is needed in order to keep track of which addresses and search paths come from where. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922578 Title: please remove 'resolvconf' from ubuntu-minimal Depends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
