* Bastian Blank <bastian+postfix-users=postfix....@waldi.eu.org> [170322 15:09]:
> Moin
> 
> On Wed, Mar 22, 2017 at 01:04:36PM -0400, Marvin Renich wrote:
> > Mar 21 14:42:45 basil postfix/smtp[12587]: 3AF35240229: 
> > to=<recipie...@host2.example2.com>, relay=none, delay=0.47, 
> > delays=0.25/0.22/0/0, dsn=4.4.3, status=deferred (Host or domain name not 
> > found. Name service error for name=florina.renich.org type=AAAA: Host not 
> > found, try again)
> 
> I looked that error up and I'm not sure if I found everything.
> 
> - "Host not found, try again" is TRY_AGAIN, according to
>   src/dns/dns_strerror.c.
> - This error is only produced if res_send produced an error, or if the
>   lookup explicitely gets a SERVFAIL.
> 
> So this message should only show up if something is already pretty wrong
> with DNS.  If there is no network it will show up for example.

Thanks for looking at this, Bastian.  Is there any reason you can think
of that res_send would fail for Postfix, but other programs, such as
host, would get a correct response?  For example, if Postfix calls
res_init, which gets a bad value from resolv.conf, like for a temporary
network outage, then Postfix continues to run for days, not requiring
any dns services.  Meanwhile, the temporary outage is short-lived, but
Postfix never gets the word.  Other programs work, but Postfix continues
to get dns failures because res_init was called at a time when
resolv.conf was bad?

...Marvin

Reply via email to