From: Tom Allison (tallisontacocat.net)
Date: Fri Jul 02 2004 - 06:44:04 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I don't see how this could have been blocked on the bases of hostname.

I can do a lookup of all the hlgllc.com addresses for both MX and A
records, but the 'dig -x' one doesn't make much sense.

tallisonisengard:~$ dig -t mx hlgllc.com +short
20 mail.microman.net.
10 mail.hlgllc.com.

tallisonisengard:~$ dig -t a hlgllc.com +short
63.64.27.245
tallisonisengard:~$

tallisonisengard:~$ dig -x 63.64.27.245 +short
245.240.27.64.63.in-addr.arpa.
host245.hlgllc.com.
tallisonisengard:~$

But it appears that doing a lookup against this one (host245.hlgllc.com)
does seem to fail. What I'm surprised at is the report that it cannot
find a hostname for 63.64.27.245.

What am I missing?
NOTE: "xxx" and "yyy" were substituted to protect the innocent.

-------- Original Message --------
Return-Path: <double-bouncecling.tacocat.net>
X-Original-To: postmaster
Delivered-To: postmastertacocat.net

Transcript of session follows.

  Out: 220 cling.tacocat.net ESMTP Postfix (Debian/GNU)
  In: EHLO mail.HLGLLC.COM
  Out: 250-cling.tacocat.net
  Out: 250-PIPELINING
  Out: 250-SIZE 10240000
  Out: 250-VRFY
  Out: 250-ETRN
  Out: 250 8BITMIME
  In: MAIL FROM:<xxxhlgllc.com> SIZE=14672
  Out: 250 Ok
  In: RCPT TO:<yyytacocat.net>
  Out: 450 Client host rejected: cannot find your hostname, [63.64.27.245]
  In: QUIT
  Out: 221 Bye

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]