[Another update to clarify, sorry, I mixed up two related issues, one about postfix name resolution and one about resolvconf + unbound.]
On 2022-01-05 15:34:38 +0100, Vincent Lefevre wrote: > On 2022-01-05 15:22:55 +0100, Andrej Shadura wrote: > > 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! /etc/resolvconf/update-libc.d actually just contains the postfix hook script, which is correct. The unbound hook script is just in /etc/resolvconf/update.d, which is also correct. So the only issue is the following, i.e. the fact that the unbound hook script is not run when the nameservers provided by DHCP (via NetworkManager) change: > 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. -- 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)
