Reverse Lookups

[Kevin Darcy]

It could be any number of things. Maybe your server is using forwarding to
resolve Internet names, but the forwarding for the reverse address space is
"blocked" by a local definition of in-addr.arpa (???)

Why don't you upgrade and then see if you still have the problem? Maybe it'll
go away. Even if it doesn't, people on this list can probably work you through
fixing it. I don't think anyone here wants to help you with debugging a
problem with a 4.9.8 nameserver though...


- Kevin

Mark Gosselin wrote:

> Hi List,
>
> I just inherited a DNS server running BIND 4.9.8 (it will be upgrading
> shortly). However, before I upgrade to 9.1,
> I have a problem I need to shake out.....
>
> Inside my own network, I can lookup by name or IP address.
>
> nslookup owl.netscout.com
>
> returns the correct IP address and a query on the IP address returns the
> proper name.
>
> However, should I look for something outside my zone, I can only find by
> name.
>
> nslookup amazon.com
>
> Returns:
>
> Name:    amazon.com
> Addresses:  207.171.181.16, 208.202.218.15
>
> nslookup 207.171.181.16
>
> Returns:
>
> *** nsisrv.netscout.com can't find 207.171.181.16: Non-existent host/domain
>
> Anyone know what could be causing this and how I can fix it??????