This is a discussion on Re: AOL still blocks Reverse DNS after it's setup within the Bind Users forums, part of the DNS and Related Forums category; In article <d0am5u$1gif$1@sf1.isc.org>, "AVB" <avanbaelen@macrotransport.com> wrote: > ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
In article <d0am5u$1gif$1@sf1.isc.org>,
"AVB" <avanbaelen@macrotransport.com> wrote: > 209.168.151.68 > I have checked it on www.dnsstuff.com and everything seems to be > correct. Thanks. Looks good to me, too. www.dnsreport.com has two FAIL checks for it, but I feel it overstates the severity of this particular problem: you have NS records pointing to ns007.deltacom.net in the zone, but not the delegation. I can't think of any way that an extra NS record in the zone can cause a failure. I think you need to write to AOL and ask them why they think there's something wrong with your reverse DNS. -- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me *** |