We had a similar problem with Qwest and, after much denial on their part, final convinced them that it was something they had to address and fix. Many levels of tech support didn't have a clue what a PTR was.
Anyway, it went something like this: Our ISP (who gets service from Qwest) got a "new" class C (their second one), and assigned us some addresses from this class C. We were still using some IP addresses on the first Class C, and didn't have a problem with DNS. But Qwest did not have this second Class C set up correctly, and had not delegated authority(?) to our ISP... So even though my ISP had the PTR set up correctly, Qwest's DNS server for this IP didn't recognize it. Finally, we convinced Qwest that they had their DNS screwed up on the Class C, and they changed it for us (wasn't that nice?). Thanks to Scott, Sandy, Len for helping me sound like I knew more than the Qwest guys (Qwest Tech: "um, how do you spell PTR?")... On a final note, the reason why this impacted us the most (that I knew of) was because Hotmail, Yahoo and AOL were rejected e-mails from my server because we didn't have the PTR set up (the way Scott has described in this thread). Once it was set up correctly, those mail servers accepted our mail. Jason Alba -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of R. Scott Perry Sent: Wednesday, July 31, 2002 8:50 AM To: [EMAIL PROTECTED] Subject: Re: [IMail Forum] PTR Record Problem >Scott, if I go to http://www.DNSstuff.com it shows that I have a PTR >reverse problem on 208.45.107.202 when I run my own primary DNS with >secondary at Qwest. This seems to come up awful fast, <G> >and I was wondering if it isn't seeing my reverse because it is >timing out on the lookup too fast. The timeouts on the reverse DNS lookup are set to 3 seconds, but if there is a timeout, it will try again (either on the same DNS server, or a different one that is authoritative for the lookup). In this case, the responses are coming very fast, but are correct. Doing a manual DNS lookup shows the same results. >My reverse are there Nope. :) >and can be seen with a simple or trace on most remote systems. I can't explain why other servers would be able to get the reverse DNS entry -- it just isn't there. ARIN directs the query to QWEST (SVL-ANS-01.INET.QWEST.NET or DCA-ANS-01.INET.QWEST.NET), but both of those report that the reverse DNS entry doesn't exist. Specifically, they report an "NXDOMAIN" response, which means that the reverse DNS entry doesn't exist. You can also go to http://www.samspade.org to verify that the reverse DNS entry doesn't exist. >Since this subject came up here, I thought I would ask. Am I >missing something here? Yes. You'll need to contact QWEST and ask them why it is reporting that there is no reverse DNS entry for 208.45.107.202. -Scott Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Please visit the Knowledge Base for answers to frequently asked questions: http://www.ipswitch.com/support/IMail/
