lookup error

[Jim Reid]

>>>>> "Ramesh" == Ramesh  <rameshr_email at yahoo.com> writes:

    Ramesh> I am using BIND 8.2.2-p5, nslookup fails sometimes soon
    Ramesh> after the named is reloaded. ndc is used for reload. Is
    Ramesh> there a bug associated with ndc or reload of named?

No. You're using nslookup which is a brain-dead, worthless piece of
junk. [Consult the list archives for more info. A search for
"nslookup" and "crap" or "sucks" will point you in the right
direction.] Use dig for DNS lookups. Come to think of it, nslookup is
worse than useless. It needlessly creates problems and confusion.

nslookup is failing because it's trying to do a reverse DNS lookup of
the address it's querying before it makes the query. When that reverse
lookup fails, you lose. As you've just found out the hard way. If you
fix the reverse lookup for 10.252.0.1, that will solve your immediate
problem with nslookup. But it still won't make nslookup a useful DNS
tool. 

BTW, 8.2.2-p5 is *very* old and has security holes. Upgrade. The
current release of BIND8 is 8.4.4. Though you'd be better off running
the current version of BIND9, 9.2.3. Details of the vulnerabilities in
old BIND versions are on the ISC web site. Which is yet another reason
for not persisting with old, buggy code that has known security issues.