On Fri, Feb 10, 2012 at 06:34:47PM -0000, Thomas Hood wrote: > 1. When resolvconf is installed it may be missing nameserver > information. I am not talking about the #923685 problem here (which > persists after reboot), just about the problem, e.g., that dhclient has > already obtained a nameserver address A at the time resolvconf is > installed and has inserted A into /etc/resolv.conf. Although the > resolvconf package has a mechanism for telling other packages to provide > nameserver information after it's installed, to date only one package > (dnsmasq) uses this mechanism. Now, resolvconf includes the pre- > installation resolv.conf in its database until the first reboot, so A > doesn't get lost. But if the dhclient-configured interface is brought > down then A is not removed from the database; so the resolver will try > that address even though it's no longer available. This malfunction goes > away after the first reboot.
My understanding is that these entries are always listed *last* by resolvconf. So the only cases where this DNS server is tried are when there are no other DNS servers known, or they all fail. I don't see how, in either case, we should worry about it trying one more incorrect DNS server in that scenario - it doesn't seem to actually negatively impact the use of the system. > 2. When resolvconf is removed it leaves a static file behind at > /etc/resolv.conf. Again, if this file contains A then A won't be > removed if the associated interface is deconfigured. Consider the case > where A is "127.0.0.1" associated with a caching nameserver which > resolvconf supplied with non-loopback nameserver addresses before it was > removed. If the caching nameserver is stopped then all nameserver > addresses will be lost. Rebooting the machine only makes a difference if something else besides resolvconf is going to update /etc/resolv.conf. With DHCP-using network interfaces this will be true (via either dhclient or NM), but in many other cases it won't be, and I'd rather not tell some users they should be rebooting needlessly. The resolvconf package is now a dependency of ubuntu-minimal anyway - it's not something that's supposed to *get* removed. So I can't really bring myself to believe this is a situation we should add code for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/929404 Title: resolvconf package should notify reboot required on installation and removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/929404/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
