Thanks all.. gives me some direction to keep digging.
-Original Message-
From: owner-postfix-us...@postfix.org On
Behalf Of Viktor Dukhovni
Sent: Monday, September 5, 2022 9:36 AM
To: postfix-users@postfix.org
Subject: Re: Odd DNS issue requiring reboot.
On Sun, Sep 04, 2022 at 10:31
On Mon, Sep 05, 2022 at 11:40:17AM -0400, Curtis Maurand wrote:
> Are you sure it's not systemd-resolvd. It will happily override your
> resolver settings if it doesn't like your resolver. I've found that in
> my setups, to install my own resolver (usually pdns-recursor) and
> disable system
On 9/5/22 11:23, Wietse Venema wrote:
Viktor Dukhovni:
Perhaps your resolver settings in the chroot jail become stale, and
are fixed when the "init script" resyncs the chroot with the /etc.
You might try running without chroot.
To turn off chroot for all Postfix daemons, update master.cf:
p
Viktor Dukhovni:
> Perhaps your resolver settings in the chroot jail become stale, and
> are fixed when the "init script" resyncs the chroot with the /etc.
> You might try running without chroot.
To turn off chroot for all Postfix daemons, update master.cf:
postconf -F "*/*/chroot = n"
postfix re
On Sun, Sep 04, 2022 at 10:31:06PM -0400, Dave Lewis - Mailinglist wrote:
> So what seems to be happening Is that if something causes a dns issue
> postfix stops sending mail, and outgoing mail queues with things like this.
>
> (Host or domain name not found. Name service error for name=gmail.com
If it requires a REBOOT, then it is not a POSTFIX problem.
Wietse
