nslookup strangness

hi,
what would cause the nslookup to work one way but not the other?

for most machine it works both ways.

>nslookup 172.18.10.235
Server:         172.16.17.3
Address:        172.16.17.3#53

235.10.18.172.in-addr.arpa      name = machine1.prod.local

>nslookup machine1
Server:         172.16.17.3
Address:        172.16.17.3#53

Name:   machine1.prod.local
Address: 172.18.10.235

but for one of the machines it only works on one direction!?!:

>nslookup machine2
Server:         172.16.17.3
Address:        172.16.17.3#53

Name:   machine2.prod.local
Address: 172.18.94.89

>nslookup 172.18.94.89
Server:         172.16.17.3
Address:        172.16.17.3#53

Non-authoritative answer:
*** Can't find 89.94.18.172.in-addr.arpa.: No answer

Authoritative answers can be found from:
.       nameserver = I.ROOT-SERVERS.NET.
.       nameserver = J.ROOT-SERVERS.NET.
.       nameserver = K.ROOT-SERVERS.NET.
.       nameserver = L.ROOT-SERVERS.NET.
.       nameserver = M.ROOT-SERVERS.NET.
.       nameserver = A.ROOT-SERVERS.NET.
.       nameserver = B.ROOT-SERVERS.NET.
.       nameserver = C.ROOT-SERVERS.NET.
.       nameserver = D.ROOT-SERVERS.NET.
.       nameserver = E.ROOT-SERVERS.NET.
.       nameserver = F.ROOT-SERVERS.NET.
.       nameserver = G.ROOT-SERVERS.NET.
.       nameserver = H.ROOT-SERVERS.NET.

any idea?

Have you checked to see if the zone "94.18.172.in-addr.arpa" is setup correctly in BIND?

--
Nate

Address to name isn't called reverse-lookup for nothing. Name to address and address to name are technically different lookups and use different files as mentioned in the previous post.

This file 89.94.18.172.in-addr.arpa. exists?

You've got this:
Non-authoritative answer:
*** Can't find 89.94.18.172.in-addr.arpa.: No answer

bye