I took a stab at writing a script to be put into /etc/dhcp3/dhclient-enter-hooks.d to try and fix this problem. It is quite simplistic, and simply unset's new_domain_name_server if the value is the same as old_domain_name_server and reason is RENEW.
The logic is, if it's a RENEW and the name server hasn't changed, then resolv.conf is either still up-to-date from when we BOUND the lease or it has been updated by some other program. In either case, we can leave resolv.conf along and assume it's contents are good. Really though, this logic should be in dhclient-script itself. After all, dhclient-script checks other important data to see if it's actually changed rather than just blindly updating it. There is no reason why the nameserver should be different. I can't think of any case where 1) it's a RENEW and 2) the nameserver hasn't changed, where updating resolv.conf is safer/better than leaving it alone. ** Attachment added: "save-vpn" http://launchpadlibrarian.net/13175077/save-vpn -- resolv.conf overwritten using VPN/PPP etc... https://bugs.launchpad.net/bugs/90681 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
