Well, I changed the permisions on /etc/resolv.conf (the exim user
couldn't read the file - blush :)
Then it took me a while to figure out that exim was smart enough to
remember that it couldn't resolve pointone.com. I cleaned the queue
and everything works.
Thanks,
^Roman
>>>>> "PH" == Philip Hazel <ph10@???> writes:
PH> On 10 Jul 2000, Roman Milner wrote:
>> Whenever I'm sending a mail with exim I get " ==
>> rmilner@??? R=lookuphost defer (-1): host lookup did
>> not complete" - I get this no matter what domain I send to.
>> (Full details with -d9 are below.)
>>
>> So, I turned on query logging on the DNS and exim is not
>> sending any query to the DNS. Calling gethostbyname() by hand
>> works, but setting gethostbyname = true in my lookuphost router
>> doesn't help. The nameserver is able to resolv this host fine.
PH> Not true. Exim is trying to look up an MX record in the DNS.
>> Below I have output for an nslookup on the domain I'm sending
>> to and from exim -d9 -M. Thanks in advance.
PH> What do you get from an nslookup that explicitly looks for MX
PH> records?
>> routing rmilner@???, domain pointone.com lookuphost
>> router called for rmilner@??? dns lookup: route_domain
>> = pointone.com DNS lookup of pointone.com (MX) gave TRY_AGAIN
PH> See? Here Exim is trying to look up an MX record, and the
PH> resolver is giving TRY_AGAIN as the result.
PH> Why this should happen is mysterious. Exim just calls the
PH> resolver in what I believe is a pretty standard way. If you
PH> run with -d11 instead of -d9 it will call the resolver with
PH> debugging turned on, so you can see the DNS queries is
PH> uses. This may give us a clue as to what is going on.
PH> My version of Exim can resolve pointone.com just fine.
PH> -- Philip Hazel University of Cambridge Computing Service,
PH> ph10@??? Cambridge, England. Phone: +44 1223 334714.
PH> -- ## List details at
PH> http://www.exim.org/mailman/listinfo/exim-users Exim details
PH> at http://www.exim.org/ ##
