Reverse IP lookup not resolving host name being forwarded

2008 Enterprise server (AD ), forwarders configured to our external dns. I
trying to do reverse lookup on an ip that is NOT in my zone (in the external
dns only), so the request should be forwarded to our external servers which
has the A record with reverse (unix). While I can lookup the host name
I.e. bigbob.bob.com that is forwarded and get a response, the reverse
10.1.1.3 lookup gives me the following error:

,<servername> can't find <ip address>: Non-existent domain

I have no issues having requests forwarded outside of our company just
specfic to our internal server.

Timeout set to 5 seconds, but I'm not getting a timeout error. Extending
timeout, doesn't seem to make any difference.

I tried this on internal 2000 and 2003 domains running AD dns, both with
success being forwarded to the same host and ip also I can retrieve outside
ip's like microsoft or dell to a reverse lookup on the 2008 domain. And
NO I don't want to put a record in the internal DNS, I shouldn't have to.

So what's gives?

In the following message:
,<servername> can't find <ip address>: Non-existent domain

Is the <IP address> given, the IP address of the <servername>? If so, it
simply means nslookup is trying to resolve the DNS server it is using, and
the server either does not have a PTR in the reverse zone for it's subnet,
or a reverse zone does not exist.

Perhaps the most complex aspects of IP are IP addressing and routing. Addressing refers to how end hosts become assigned IP addresses and how subnetworks of IP host addresses are divided and grouped together. IP routing is performed by all hosts, but most importantly by internetwork routers, which typically use either interior gateway protocols (IGPs) or external gateway protocols (EGPs) to help make IP datagram forwarding decisions across IP connected networks the reverse iP doesnt resolve the issue great you can check out your detail in http://www.ip-details.com/.. Thank you...