Odd reverse lookup failures

[Kevin Darcy]

You left one very important detail out of your message: the address or addresses having the problem. Makes troubleshooting just a tad easier...

                                                                                                                                                    - Kevin

Forrest Aldrich wrote:

> Recently, we've began seeing some sporatic problems performing reverse lookups of our IP zones.
>
> The first complaint came in from someone attempting to access ftp.geocities.com.   I performed a reverse lookup against their servers and got different results.  Their primary, NS2.GEOCITIES.COM, reported an error (no A records available), but their secondary provided the correct answer.   Their tertiary servers, owned by Yahoo, also failed to provide reverse.
>
> Second, I tried against a.root-servers.net, and got the correct response, but got failures from b, c, ... et al.
>
> We've see the same results across the board (ie: running lookups against different name servers around the globe).
>
> What's perplexing, is that nothing has really changed on our servers... and recently, NS2.GEOCITIES.COM suddely began reporting the correct information.
>
> Our zones look like this:
>
> Forward:
>
> hostname        IN      A       xxx.xxx.xxx.xxx
>
> Reverse:
>
> (SOA header xx.xx.xx.in-addr.arpa ...)
> xxx             IN      PTR     hostname.ourdomain.net.
>
> One thing that occurred to me is that presently our ARIN record points our DNS servers to our .COM name rather than the real .NET name -- though I have A records for the .COM, the reverse points to .NET.    We've submitted a Modify for these -- and I can't see where this would be a problem.
>
> This is very perplexing.  I've combed our configuration over several times, and I can't find anything wrong.
>
> Has anyone experienced this?   I'd appreciate any info about this one....
>
> TIA.