sendmail - reverse lookup problems
barmar at genuity.net
Tue Oct 9 19:53:51 UTC 2001
In article <9pvgr8$9av at pub3.rc.vix.com>,
Boex,Matthew W. <Matthew.Boex at cna.com> wrote:
>another odd problem with reverse lookup's. we are able to send mail to
>na.bestfoods.com [126.96.36.199]. They cannot send mail to us. They can do
>an nslookup and get our mx record. Sendmail, on our end, I think is timing
>out trying to reverse lookup their outbound mail server. They tell me the
>server is 188.8.131.52. when i do an nslookup 184.108.40.206 i get nothing.
>when i do a dig -x 220.127.116.11 it reports that att.net is authoritative for
>their domain, and the PTR record is aliased? i think.
They're doing RFC 2317-style reverse DNS, but there's no PTR record for the
..35 address. The only reverse entry they have in that block is for the .10
>why is nslookup showing nothing
Because nslookup sucks. You knew that already, didn't you?
>why is sendmail choking on an aliased PTR record? Should it be choking?
The problem isn't that it's aliased, it's that the thing it's aliased to
doesn't exist. You have sendmail configured to require a reverse DNS entry
for the client, and they don't have one.
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users