Sam,
After implementing some anti-spam features in my mail server, I noted that BT3Central's reverse DNS isn't set up. To wit:
jb2@loki keep $ nslookup mail.bt3central.com
Non-authoritative answer:
Name: mail.bt3central.com
Address: 198.247.173.131
jb2@loki keep $ nslookup 198.247.173.131
** server can't find 131.173.247.198.in-addr.arpa: NXDOMAIN
I also noticed that mail sent from BT3Central comes from 198.247.173.242, which doesn't have it's reverse DNS set up either:
jb2@loki keep $ nslookup 198.247.173.242
** server can't find 242.173.247.198.in-addr.arpa: NXDOMAIN
I believe the relevant RFC's state that all mail servers are supposed to be resolvable in both directions. It doesn't necessarily have to resolve to a BT3Central address, but it's supposed to resolve to something.
I just thought you might like to know.
Jeff
After implementing some anti-spam features in my mail server, I noted that BT3Central's reverse DNS isn't set up. To wit:
jb2@loki keep $ nslookup mail.bt3central.com
Non-authoritative answer:
Name: mail.bt3central.com
Address: 198.247.173.131
jb2@loki keep $ nslookup 198.247.173.131
** server can't find 131.173.247.198.in-addr.arpa: NXDOMAIN
I also noticed that mail sent from BT3Central comes from 198.247.173.242, which doesn't have it's reverse DNS set up either:
jb2@loki keep $ nslookup 198.247.173.242
** server can't find 242.173.247.198.in-addr.arpa: NXDOMAIN
I believe the relevant RFC's state that all mail servers are supposed to be resolvable in both directions. It doesn't necessarily have to resolve to a BT3Central address, but it's supposed to resolve to something.
I just thought you might like to know.
Jeff
Comment