On Thu, Jan 03, 2008 at 09:45:56PM +0100, Marten Lehmann wrote:
> I was very astounded to see these lines in my logfile:
>
> 2008-01-03 09:21:10 1JALK9-0008H5-JN <= support@??? H=(cath)
> [217.83.41.105] P=esmtpa A=dbm_login:user@??? S=968 for
> user@??? support@???
> 2008-01-03 09:21:10 1JALK9-0008H5-JN == user@???
> R=dnslookup defer (-1): host lookup did not complete
> 2008-01-03 09:21:10 1JALK9-0008H5-JN ** user@???: retry
> timeout exceeded
>
> The real domain name (replaced by otherexample.com) is resolvable for
> years now. There are two nameservers available and even if both
> shouldn't be able to answer, exim should try it a second time. Why
> doesn't exim try it again in this case (all happened within one second)?
Hard to say since you obfuscated the domain name, there's no way any
of us can test to see if there is a problem with the authoritative DNS
for that domain.
http://wiki.exim.org/DontObfuscate
It might be a problem with your local system, but there's not enough
information here to go on. Clearly DNS isn't (or wasn't at that time)
resolving properly for that domain though, at least on that local machine.
The "retry timeout exceeded" simply means what it says. DNS lookups
from Exim's point of view have been failing for a while and the timeframe
has passed the longest retry time value.
--
Dean Brooks
dean@???
