simple local caching DNS

[Clarence Brown]

Well, I guess I'm a little unsure of having a reverse zone without 
a forward zone.... What are the ramifications of that? 

Maybe a "fake" internal zone? 

How **__SHOULD__** this be handled?

Thanks, Cla.

----- Original Message ----- 
From: "Charles Cala" <charles_cala at yahoo.com>
> 
> --- Clarence Brown <clabrown at granitepost.com> wrote:
>  
> > c:\>nslookup
> > *** Can't find server name for address 10.15.10.2: Non-existent domain
> > Default Server:  ns1.sprintlink.net
> > Address:  204.117.214.10
> 
> Lots of people are going to say that nslookup is broken, 
> and windows is super broken ( I agree that windows is broken) 
> however the issue with nslookup is that 
> __ nslookup is functioning as written __ .
> 
> It is trying to do a forward/reverse lookup on the local name server 
> and failing. You can "fix" this by adding a reverse zone for the private 
> address space you have  your machines in. Be aware that sprintlnk  
> won't have that  info.
> 
> -charles
> 
> 
>