On 2022-01-05 15:22:55 +0100, Andrej Shadura wrote: > Hi, > > On Wed, 5 Jan 2022, at 15:17, Vincent Lefevre wrote: > > 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!
Oops, I forgot /etc/resolvconf/update.d/unbound, but it isn't run either, even if the nameservers change, e.g. from zira:~> cat /run/resolvconf/interface/NetworkManager nameserver 127.0.0.1 nameserver 192.168.43.31 to zira:~> cat /run/resolvconf/interface/NetworkManager nameserver 127.0.0.1 nameserver 192.168.1.1 So this may be a bug in resolvconf after all, since this script is supposed to be run when nameserver information has changed. > Having looked at it again, it seems Thomas, the original author of > resolvconf, have actually included a workaround for your use case. > Set TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no in > /etc/default/resolvconf, and it should do the thing. Well, the bug needs to be fixed to avoid the workaround. Or the workaround should be the default. -- 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)
