(no subject)

[Kevin Darcy]

Maybe, maybe not. You haven't shown us your named.conf file or any of
your zone files, so who can know for sure?

Your immediate problem is that nslookup can't do a reverse lookup of
10.0.5.1. Does this indicate a larger problem? Don't know. Or does it
indicate simply that nslookup sucks and you should use a real lookup
tool like "dig" instead? Maybe.

I will note, however, that if you are using a private, RFC 1918,
"Moskoblock" address range like 10/8, and you're sending queries to the
Internet, you really should set up a 10.in-addr.arpa zone to prevent any
10.*.*.* reverse queries leaking out onto the Internet. (Whether your
choose to delegate subzones of 10.in-addr.arpa is purely optional).


- Kevin

Ravi Nair wrote:

> setup :-
> --Running BIND 8.2.3 on solaris 2.6
> --created named.boot and converted to named.conf using
> the named-bootconf
> --- created zone files with TTL entries
> --- modified resolv.conf file to point to name server
> ---- ran /etc/named and checked the process running.
> Observation-
>
> did an nslookup to a domain name (on dns server
> itself)
> ---returns error message 'can't find server name for
> address '10.0.5.1'(internal address of DNS server )
>
> Is anything wrong.Pl respond asap
> Thanks
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/