On 27.08.2025 22:08, Matthew via Postfix-users wrote:
Hi Michael,
So cool to have a message from the actual Debian package maintainer via
here too!
I've been here on this list for almost 25 years :)
As you requested:
root@SMTP:~# ls -l /var/spool/postfix/etc/resolv.conf
-rw-r--r-- 1 root root 114 Aug 27 19:22 /var/spool/postfix/etc/
resolv.conf
root@SMTP:~# ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 162 Aug 27 19:23 /etc/resolv.conf
Aha. So my guess wasn't right.
I think it's just as simple as the service is starting too early (before
dhcpd has concluded).. I looked more at whether network-online.target
was a viable option and it looks like in non-GUI Trixie there's nothing
that implements or depends on it. ChatGPT suggested some pre-script that
if it came to it just implements a crude delay before Postfix gets started.
Which dhcp do you use? Postfix provides hooks to update resolv.conf
but only for well-known dhcp daemons, - which aren't many in debian
these days.
By delaying things, you wont get it fixed, - because if you'll have
different resolv.conf after next dhcp lease update, it wont be
propagated, but should.
At this point, there are several options available. I'd suggest to
follow advice by Wietse and un-chroot at least services in question.
In debian we ship postfix-resolvconf.path unit which can be used to
update in-chroot resolv.conf when /etc/resolv.conf changes, you can
enable it.
Depending on your email volume, it might be a good idea to run local
caching nameserver - even something as simple as dnsmasq would do,
systemd-resolved works, unbound, or bind9. That'd be 3rd option.
Thanks,
/mjt
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
