Re: [Exim] hostname lookups fail - nameserver never gets que…

Página Principal
Apagar esta mensagem
Responder a esta mensagem
Autor: Roman Milner
Data:  
Para: Philip Hazel
CC: exim-users
Assunto: Re: [Exim] hostname lookups fail - nameserver never gets queried
Thanks for the quick response.

>>>>> "PH" == Philip Hazel <ph10@???> writes:


    PH> What do you get from an nslookup that explicitly looks for MX
    PH> records?


Here is the output from an nslookup with set type=mx followed by a
set type=a and a lookup of the cheapest mx record hostname.


root@pbob /usr/local/exim/bin# nslookup
Default Server: pbob.speeder.org
Address: 192.168.0.1

> set type=mx
> pointone.com

Server: pbob.speeder.org
Address: 192.168.0.1

Non-authoritative answer:
pointone.com    preference = 15, mail exchanger = ns1.pointone.com
pointone.com    preference = 10, mail exchanger = mail.pointone.com


Authoritative answers can be found from:
pointone.com    nameserver = ns1.pointone.com
pointone.com    nameserver = NS2.pointone.com
pointone.com    nameserver = NS1.dbcity.com
pointone.com    nameserver = NS.dbcity.com
ns1.pointone.com        internet address = 209.217.128.11
mail.pointone.com       internet address = 209.217.128.2
NS2.pointone.com        internet address = 209.217.128.12
NS1.dbcity.com  internet address = 208.2.77.26
NS.dbcity.com   internet address = 208.2.77.19

> set type=a
> mail.pointone.com

Server: pbob.speeder.org
Address: 192.168.0.1

Non-authoritative answer:
Name:    mail.pointone.com
Address:  209.217.128.2


>


    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.


OK, here is the -d11 output. As far as I can see - there doesn't seem
to be much new about the DNS query - but maybe I missed something. I
tried switching my DNS in resolv.conf and this didn't help.

Thanks,
^Roman




Exim version 3.15 debug level 11 uid=0 gid=0
Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)
pbob.speeder.org in local_domains? yes (matched pbob.speeder.org)
Actual local interface address is 127.0.0.1
Actual local interface address is 24.27.51.96
Actual local interface address is 192.168.0.1
Caller is an admin user
Caller is a trusted user
set_process_info: 3985 3.15 delivering specified messages
delivering message 13BXP0-0000Xi-00
set_process_info: 3985 3.15 delivering 13BXP0-0000Xi-00
Opened spool file 13BXP0-0000Xi-00-H
user=root uid=0 gid=0 sender=root@???
sender_local=1 resent=no ident=root
Non-recipients:
Empty Tree
---- End of tree ----
recipients_count=1
body_linecount=2 message_linecount=7
Delivery address list:
rmilner@???
locked /usr/local/exim/spool/db/retry.lockfile
opened DB file /usr/local/exim/spool/db/retry: flags=0
>>>>>>>>>>>>>>>>>>>>>>>>

Considering: rmilner@???
pointone.com in local_domains? no (end of list)
unique = rmilner@???
dbfn_read: key=R:pointone.com
dbfn_read: key=R:rmilner@???
rmilner@???: queued for routing
>>>>>>>>>>>>>>>>>>>>>>>>

After directing:
  Local addresses:
  Remote addresses:
  Failed addresses:
  Addresses to be routed:
    rmilner@???
  Deferred addresses:

>>>>>>>>>>>>>>>>>>>>>>>>

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
pointone.com in dns_again_means_nonexist? no (end of list)
returning DNS_AGAIN
lookuphost router deferred pointone.com
message: host lookup did not complete
added retry item for R:pointone.com: errno=-1 0 flags=0
post-process rmilner@???
LOG: 0 MAIN
== rmilner@??? R=lookuphost defer (-1): host lookup did not complete
search_tidyup called
set_process_info: 3985 3.15 tidying up after delivering 13BXP0-0000Xi-00
Processing retry items
Succeeded addresses:
Failed addresses:
Deferred addresses:
rmilner@???
locked /usr/local/exim/spool/db/retry.lockfile
opened DB file /usr/local/exim/spool/db/retry: flags=42
pointone.com in *? yes (*)
retry for R:pointone.com = *
dbfn_read: key=R:pointone.com
Writing retry data for R:pointone.com
first failed=963207032 last try=963218566 next try=963225766 expired=0
error -1 0: host lookup did not complete
dbfn_write: key=R:pointone.com
end of retry processing
time on queue = 1h51m56s
warning counts: required 0 done 0
delivery deferred: update_spool=0 header_changed=0
end delivery of 13BXP0-0000Xi-00