nslookup bugs!!!

[Jim Reid]

>>>>> "Shabir" == Shabir ahmed <shabir at cyber.net.pk> writes:

    Shabir> Dear All, i'm configuration our dns (202.163.96.134). when
    Shabir> i run nslookup it gives me errors:

    Shabir> *** Can't find server name for address 202.163.96.134: Non-existent host/domain
    Shabir> *** Default servers are not available

    Shabir> it even work if i enter 127.0.0.1 in resolv.conf

    Shabir> i have resolv.conf entry: 
    Shabir> domain cyber.net.pk 
    Shabir> nameserver 202.163.96.134

    Shabir> Any suggestions!!!!

First of all, stop using nslookup. It's awful. Use dig for checking
name servers and performing DNS lookups. Throw nslookup in the bin.
Your next problem is that you have configured the resolver to send DNS
queries to IP address 202.163.96.134, but this host does not appear to
be running a name server. [Using the loopback interface (127.0.0.1) is
equally pointless if the local machine isn't running a working name
server.] The next problem is that reverse lookups of 202.163.96.134
don't work. This is one of the idiotic things that nslookup depends
on. If nslookup can't do a successful reverse lookup of the address
it's querying, it fails. Why this happens is a mystery. It's one of
the annoying and unnecessary irritations that makes nslookup such an
abysmal tool.

None of the behaviour you describe can be attributed to bugs in
nslookup. It's behaving the (usually stupid and confusing) way it was
designed to work. Your problems really lie in misconfiguration.
Pointing DNS queries at a non-existent name server is not likely to
have a successful outcome.