PTR Record with a valid Reverse DNS entry??

I am repeatedly getting this message. What is a "PTR record with a
valid Reverse DNS entry"? And can this be controlled by me or is it a
problem with Gmail or the Washington Post or Comcast? Thanks.

----- Transcript of session follows -----
.... while talking to mx2.comcast.net.:
<<< 554 IMTA16.emeryville.ca.mail.comcast.net comcast 12.129.147.8
Comcast requires that all mail servers must have a PTR record with a
valid Reverse DNS entry. Currently your mail server does not fill that
requirement. For more information, refer to:
http://www.comcast.net/help/faq/inde...il_Policy18784
.... while talking to mx1.comcast.net.:

sryeasted@gmail.com

On Sat, 1 Dec 2007 08:30:20 -0800 (PST), sryeasted wrote:

>I am repeatedly getting this message. What is a "PTR record with a
>valid Reverse DNS entry"? And can this be controlled by me or is it a
>problem with Gmail or the Washington Post or Comcast? Thanks.

Not you.

Where does the WP get involved in this, is that where you are sending
mail to?

Speak to the service that provides your internet connection / the mail
service you yse if it isn't your ISP.

PTR record, reverse and mail , read the info
http://aplawrence.com/Blog/B961.html


> ----- Transcript of session follows -----
>... while talking to mx2.comcast.net.:
><<< 554 IMTA16.emeryville.ca.mail.comcast.net comcast 12.129.147.8
>Comcast requires that all mail servers must have a PTR record with a
>valid Reverse DNS entry. Currently your mail server does not fill that
>requirement. For more information, refer to:
>http://www.comcast.net/help/faq/inde...il_Policy18784

The FAQ states the issue clearly, and says how to resolve.

Why ask?

>... while talking to mx1.comcast.net.:

Me

<> wrote in message
news:91a189ea-3181-4da8-9db2-...
>I am repeatedly getting this message. What is a "PTR record with a
> valid Reverse DNS entry"? And can this be controlled by me or is it
> a
> problem with Gmail or the Washington Post or Comcast? Thanks.
>
> ----- Transcript of session follows -----
> ... while talking to mx2.comcast.net.:
> <<< 554 IMTA16.emeryville.ca.mail.comcast.net comcast 12.129.147.8
> Comcast requires that all mail servers must have a PTR record with a
> valid Reverse DNS entry. Currently your mail server does not fill
> that
> requirement. For more information, refer to:
> http://www.comcast.net/help/faq/inde...il_Policy18784
> ... while talking to mx1.comcast.net.:


It means YOUR mail service is fucked up. YOUR e-mail provider is not
providing a reverse lookup from their own nameserver, so Comcast
rejects getting e-mail from your service (AOL will do the same thing).
Not only should your e-mail provider include an IP name to IP address
lookup in their own nameserver but they should also be included an MX
record for every valid mail host on their domain that is authorized to
send e-mail from their domain. Your e-mail provider is refusing to
too stupid to identify their sending mail host to the receiving mail
hosts.

http://www.saas.nsw.edu.au/solutions/dns.html
http://postmaster.info.aol.com/info/rdns.html

Good luck trying to get anyone at Google to see your message to them
saying that, as a customer, you want to report their nameserver is
screwed up.

<> wrote in message
news:91a189ea-3181-4da8-9db2-...
>I am repeatedly getting this message. What is a "PTR record with a
> valid Reverse DNS entry"? And can this be controlled by me or is it a
> problem with Gmail or the Washington Post or Comcast? Thanks.
>
> ----- Transcript of session follows -----
> ... while talking to mx2.comcast.net.:
> <<< 554 IMTA16.emeryville.ca.mail.comcast.net comcast 12.129.147.8
> Comcast requires that all mail servers must have a PTR record with a
> valid Reverse DNS entry. Currently your mail server does not fill that
> requirement. For more information, refer to:
> http://www.comcast.net/help/faq/inde...il_Policy18784
> ... while talking to mx1.comcast.net.:

All 3 listed mail servers comply, so, are you on a network - workplace
or maybe internet cafe etc, or are you anonymously bulk mailing?
If not then it was probably just a hiccup and resolved by now.
http://support.microsoft.com/kb/924235/en-us
http://support.microsoft.com/kb/171789/en-us