On Fri, 26 Jan 2007, W B Hacker wrote:
>
> Their message may not say so specifically, but I would suspect rDNS and/or
> forward/reverse lookup mismatch:
>
> triligon# dig ptr whmoseley.com
>
> ; <<>> DiG 9.3.2-P1 <<>> ptr whmoseley.com
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49648
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;whmoseley.com. IN PTR
>
> ;; AUTHORITY SECTION:
> whmoseley.com. 10800 IN SOA ns1.hank.org.
> hostmaster.whmoseley.com. 2004022241 86400 3600 604800 86400
>
>
> And then:
>
> triligon# host 63.205.225.170
> 170.225.205.63.in-addr.arpa is an alias for 170.168.225.205.63.in-addr.arpa.
> 170.168.225.205.63.in-addr.arpa domain name pointer mardy.hank.org.
>
> Besides the IP aliasing, mardy.hank.org and mail.whmosely.com do not match, even
> if their lookup proceeds that far...
>
I doubt att cares about forward/reverse matching on a destination
they mail to.
It's more likely some network issue or firewall entry (perhaps at att's
end) means they can't get to the NSen for whmoseley.com. Which are both
in the same /24.
--
--------------------------------------------------------
Dave Lugo dlugo@??? LC Unit #260 TINLC
Have you hugged your firewall today? No spam, thanks.
--------------------------------------------------------
Are you the police? . . . . No ma'am, we're sysadmins.
