This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Found a workaround to the problem. By replacing the fully qualified
domain name in my resolv.conf file with the ip address of the dns server
it started working.
original resolv.conf:
search
nameserver ns1.helpfulhome.com
nameserver authns1.mpls.qwest.net
nameserver authns2.dnvr.qwest.net
nameserver 168.103.24.1
nameserver 204.147.80.1
new resolv.conf
search
nameserver 207.224.115.73
nameserver authns1.mpls.qwest.net
nameserver authns2.dnvr.qwest.net
nameserver 168.103.24.1
nameserver 204.147.80.1
Now I grant that Qwest has my reverse DNS totally hosed. But other mail
servers are finding me just fine and dig and nslookup were both able to
find the record without any delay. I would dearly like to know if this
is a bug in exim or ???? All other packages on the system worked and
continue to work fine (apache, ssh, cocoon, tomcat, telnet, proftp...)
Let me know what other information you would like....
Original Message
============================================================
At my wits end on this one. I have a debian 3.0 box running 4.20 kernel
and exim 4.20. I have configured the system for a plain jane delivery
of hosts on a 192. net to outside hosts. Any delivery at all (even form
a client on the box) fails to do the DNS lookup.
If I run exim in debug here is an example of the output:
|12303 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
12303 routing keith@???
12303 --------> dnslookup router <--------
12303 local_part=keith domain=alistmail.net
12303 checking domains
12303 alistmail.net in "@ : bad.com : good.com : new.com"? no (end of list)
12303 alistmail.net in "! +local_domains"? yes (end of list)
12303 calling dnslookup router
12303 dnslookup router called for keith@???
12303 domain = alistmail.net
12303 DNS lookup of alistmail.net (MX) gave TRY_AGAIN
12303 alistmail.net in dns_again_means_nonexist? no (option unset)
12303 returning DNS_AGAIN
12303 dnslookup router: defer for keith@???
12303 message: host lookup did not complete
12303 added retry item for R:alistmail.net: errno=-1 0 flags=0
12303 post-process keith@??? (1)
12303 LOG: MAIN
12303 == keith@??? R=dnslookup defer (-1): host lookup did
not complete
12303 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
|
yet if I kill exim and run dig at the same command prompt (ie. same
environment) I get:
|# dig alistmail.net MX
|
|; <<>> DiG 9.2.1 <<>> alistmail.net MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34290
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;alistmail.net. IN MX
;; ANSWER SECTION:
alistmail.net. 604800 IN MX 0 wilson.alistmail.net.
;; AUTHORITY SECTION:
alistmail.net. 604800 IN NS birch.HelpfulHome.net.
;; ADDITIONAL SECTION:
wilson.alistmail.net. 604800 IN A 168.103.92.138
;; Query time: 91 msec
;; SERVER: 207.224.115.73#53(ns1.helpfulhome.com)
;; WHEN: Sat Jul 19 11:29:29 2003
;; MSG SIZE rcvd: 102
|The dig lookup completes immediately (less than half a second) as does
nslookup. Also, ping immediately looks up the address and is able to
ping the mail host.
|
|This is just an example domain, all domains fail even popular
destinations like yahoo. I am sure that this is a short circuit in my
DNS resolver, but it only seems to affect exim. This was originally a
3.x exim install from the debian dists. I yanked it when it did exactly
the same thing. I just thought it would be easier for the group to help
me with the problem on a current version...||
|||
|
--
