error in nslookup

Jim Reid jim at rfc1035.com
Wed May 17 14:14:24 UTC 2000


>>>>> "Allan" == Allan T Parreno <allan at iloilo.fapenet.org> writes:

    Allan> got error when i run the nslookup. The Primary DNS is
    Allan> ns1.1speedcom.com and ip was 202.134.244.129, then the
    Allan> ns2.1speedcom.com and ip address 202.134.244.130 is the
    Allan> secondaryDNS. actually the secondary DNS is still down.

    Allan> [root at ns1 named]# nslookup 
    Allan> *** Can't find server name for address 202.134.244.129: Non-existent host/domain 
    Allan> *** Can't find server name for address 202.134.244.130: No response from server
    Allan>  *** Default servers are not available

    Allan> Anyone can suggest me what to do or where do i fixed it?

First of all, stop using nslookup. It is a truly dreadful bit of
software. Use dig or host - both shipped with BIND - for making DNS
lookups and troubleshooting. dig is the generally favoured tool. Your
second problem is that reverse lookups for 202.134.244.129 don't
work. There's no mapping of this IP address to a hostname. [One of
nslookup's many annoying quirks is that it does a reverse lookup of
the name server it queries and gets upset if that lookup fails. Why
nslookup wastes effort on this confusing, irrelevant and unnecessary
distraction is a mystery.] You can fix that error by updating the
244.134.202.in-addr.arpa zone. BTW, reverse lookups for all your IP
addresses should work regardless of whether they run name servers or
not. Your next problem is resolv.conf. You have told the resolver to
send queries to 202.134.244.130 even though you know that this host
doesn't have a working name server. You should only provide the
addresses of up to 3 name servers that are normally always up and
running in this file.



More information about the bind-users mailing list