19.04.2022 17:49, Vincent Lefevre wrote:
..
I don't think this is in the scope of resolvconf people, because
the whole purpose of resolvconf is different.
I don't know what you mean here. In my case, the purpose of resolvconf
is just to restart postfix each time /etc/resolv.conf is modified
resolvconf does not "check" updates of resolv.conf, it *manages*
resolv.conf and maintains a list of available nameservers, including
nameservers provided by DHCP.
[]
I tend to close this bug report, Vincent. This is not the intended
usage of resolvconf, and is not something to fix in unbound, either.
Unbound can either accept whatever resolvconf gives it from dhcp and
use that as its own forwarders (with the the script in $subject
enabled), or it can continue to perform recursive queries as before,
starting with the root nameservers. There's no such thing as a
"fallback" here, at all.
Then this should be a resolvconf bug. But the fix on the postfix side
There's no bug per se, at least I still can't see one.
And there's no "fallback" here. either.
(Debian bug 1003152) makes resolvconf no longer needed. So, as long
as other Debian packages do not need resolvconf, I no longer care
about it.
Well, systemd already have its own nameserver configuration and its
own resolver cache which does not need any reload of daemons, since
resolv.conf does not change (It does not change with resolvconf and
unbound running with resolvconf hook enabled, either, and postfix
already needs no restart).
Thank you for your patience!
/mjt
