Dave Lugo wrote:
> 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.
Duhhh.. of course...
>
> 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.
>
I've now run several 'ping' on both whmoseley.com and mail.whmoseley.com and get
a response on the mx but not on the domain.tld
Digging @ns1.hank.org and @ns2.hank.org finds that the record type is odd.
i.e. there is an 'A' record as well as an 'MX' record for the mailserver, but no
'A' record for the bare domain.tld.
If it were my domain, I would:
- add an 'A' record for whmoseley.com
- pull the 'A' record for mail.whmoseley.com
- optionally add an 'MX' record for mx.whmoseley.com
(some folks do seek that....)
JM2CW,
Bill
dig @ns1.hank.org mx whmoseley.com
