On 2022-01-05 15:56:33 +0100, Andrej Shadura wrote: > Hi, > > On Wed, 5 Jan 2022, at 15:34, Vincent Lefevre wrote: > > 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. > > By default resolvconf truncates on localhost, so the resulting file > doesn’t change. I guess I need to give it a bit more though.
This means that the hook scripts in /etc/resolvconf/update-libc.d will not be run. But the hook scripts in /etc/resolvconf/update.d should still be run, as documented in the resolvconf(8) man page. I can see: zira:~> ll /etc/resolvconf/update.d total 12 -rwxr-xr-x 1 root root 4641 2021-12-28 22:36:01 libc* -rw-r--r-- 1 root root 661 2022-01-05 15:36:36 unbound While "libc" is executable, "unbound" is not. This may be the cause of the bug (the resolvconf(8) man page is not explicit about the behavior). I'm going to do some tests. > In any case though, you probably shouldn’t prepend localhost in your > DHCP config, but rely on unbound’s integration instead. This is needed if resolvconf is not installed. This is not the cause of the bug, anyway. -- 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)
