On 2022-04-19 19:11:42 +0300, Michael Tokarev wrote: > 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.
My point is that the postfix package provides a resolvconf hook to restart postfix when /etc/resolv.conf changes: /etc/resolvconf/update-libc.d/postfix This is why resolvconf is the recommended way to make sure that postfix uses up-to-date nameservers. > 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). But AFAIK, it doesn't have a way to fall back to the nameservers provided by DHCP. -- 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)
