On 2022-01-05 15:11:04 +0100, Vincent Lefevre wrote: > After testing, /etc/resolvconf/update.d/unbound isn't run at all: > I've added "logger /etc/resolvconf/update.d/unbound" at the beginning > of this script, and it doesn't appear in the logs. > > So this seems to be a resolvconf bug.
Well, perhaps not. The resolvconf(8) man page says: When nameserver information is updated, the script /etc/resolvconf/update.d/libc generates a new version of the resolver configuration file, /run/resolvconf/resolv.conf, as described below. If the new version of the file differs from the previously generated one then the hook scripts found in /etc/resolvconf/update-libc.d/ are executed. What happens with unbound is that /run/resolvconf/resolv.conf *always* contains "nameserver 127.0.0.1", i.e. this file never changes, even though the DHCP-provided nameservers (which are not listed in this file) do. So putting the unbound hook script in this /etc/resolvconf/update-libc.d directory is very silly! -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
