On Wed, 5 Jan 2022, at 16:10, Vincent Lefevre wrote: >> 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.
unbound (1.5.7-2) unstable; urgency=medium * debian/rules: Disable the resolvconf update.d hook by default I guess this is it. No idea why, no explanation. -- Cheers, Andrej
