On 2021-12-29 16:38:15 -0500, Scott Kitterman wrote: > On Wednesday, December 29, 2021 3:26:00 PM EST Vincent Lefevre wrote: > > I don't have resolvconf installed (it is not installed by default). > > If you think that this is the way this should be done, then perhaps > > postfix should recommend resolvconf. > > Thanks. I'll do some research and figure something out. Can you verify that > installing resolvconf solves the problem?
After installing resolvconf, I can see that /etc/resolv.conf has been updated and that /var/spool/postfix/etc/resolv.conf has been changed to have the same content. So I assume that this solves the problem. This doesn't change much on this machine since I'm using unbound, so that /etc/resolv.conf will never change (by default, resolvconf truncates after the local nameserver, though I may change its config if I see that this yields problems: in the past, on another machine, I got timeout problems with the default resolvconf config + bind in case of many requests at the same time, but I hope that unbound is better than bind). -- 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)
