Philip Hazel wrote:
> It's certainly an Exim error in that it shouldn't ever encounter that,
> but it could be a bug in the resolver library that is provoking it.
I have other problems with Exim on AIX, so this may very well be the
case. I am looking into these problems, too, but for the moment I
managed to get around them. But this one looks like a show stopper at
the moment.
> I tried "exim -bh 207.16.104.250" on a Linux box and it did not have a
> problem with the reverse lookup - it just found a large number of names
> for the IP address. So it looks like it is specific to your system.
> Please try the test again, adding "-d+resolver" to the Exim command.
> That should turn on the resolver's debugging output, which might offer
> some clue.
looking up host name for 207.16.104.250
;; res_nquerydomain(250.104.16.207.in-addr.arpa, <Nil>, 1, 12)
;; res_query(250.104.16.207.in-addr.arpa, 1, 12)
;; res_nmkquery(QUERY, 250.104.16.207.in-addr.arpa, IN, PTR)
;; res_send()
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21411
;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; 250.104.16.207.in-addr.arpa, type = PTR, class = IN
;; Querying server (# 1) address = 132.252.1.7
;; truncated answer
;; Querying server (# 1) address = 132.252.1.7
;; response truncated
;; got answer:
;; ns_initparse: Message too long
LOG: MAIN PANIC DIE
internal error: store_reset(539560499) failed: pool=1 host.c 1246
Looks like the answer is indeed too long, so Exim (or the resolver lib?)
should retry via TCP.
--
Harald Schueler
