simple task - just can't do it... internal name cache

Kevin Darcy kcd at daimlerchrysler.com
Thu Aug 10 23:04:30 UTC 2000


nslookup sucks. Use dig instead. nslookup is failing over because it can't
reverse-resolve 192.168.1.34. Do you have a reverse zone set up for that? dig
doesn't have such problems.


- Kevin

Tariq Rashid wrote:

> i'm using a linux mandrake box (7.1) ... i want it to cache names for my
> internal net (192.168.1.*)
>
> i did the rpm -Uvh for the bind and caching-namserver rpms from mandrake
>
> i'm reading all the HOWTOs and even Sun's documentation too!!
>
> PROBLEML: on the server itself (127.0.0.1) i can use nslookup with no
> problem
> /etc/resolve.conf contains 127.0.0.1, and two external nameservers.
> nslookup reports things fine
>
> now... when i get ANOTHER machine to use this nameserver it won;t work.
> the clients /etc/resolv.conf has the ip of this namerver and two other
> outside namservers.
> nslookup falls back to the external ones.
>
> the error message is:
>   nslookup
>   *** Can't find server name for address 192.168.1.34: Non-existent
> host/domain
>   Default Server:  ns0.corpex.net
>   Address:  195.153.247.10
>
> 192.168.1.34 is the planned nameserver
>
> why won't the clients see this server. ping works. telnet works. its in the
> /etc/hosts...???
>
> i don't have a domain registered... i only want the one box to cache all
> name lookups to the outside world for the rest to use.
>
> any suggestions?
>
> tariq rashid






More information about the bind-users mailing list