Re: [exim] Bug in DNS resolver or in DNS setup?

> exim -d+all -bh 83.223.83.9 should give the results of the
> gethostbyname2 calls done by exim. But I guess it's just your resolver
> not replying fast enough to exim's query so it times out.

Exim deals with errors returned by the resolver, and although the code
is not pretty (somehow no code dealing with resolving is), by now I am
pretty convinced of its robustness.

> awk '/no IP address found for/{ print $9 }' mainlog | xargs -l1 host
>
> Gives all NXDOMAIN results here.

I learned a whole lot about what you can screw up during the last hours.
My favourite: Use a different glue A record in the TLD zone and in the
delegated zone, but have both servers answer authoritative for the zone.
More obvious: Use different NS names at the registry and in the zone,
all of them answering authoritative, but with different results.

Then of course you have regular lame delegations and, as always,
different serials.

All NXDOMAIN? Lucky you, but thanks for looking.

Unfortunately, that does not solve the problem. I log the result of
the gethostbyname2() call now, and of course I have not had a single
problem since, that could not be explained.

Michael