simple local caching DNS

AL al.minor at
Mon Nov 29 22:19:05 UTC 2004

The answer is in the message what it is telling you is to make sure
that the DNS server name and ip address exist on the first server that
nslookup queries.  Simply create a ptr record or a cname record and
the wizard should step you through it.  Also make sure you do the same
on all the other dns servers as well each server must have a record
about the other.

"Clarence Brown" <clabrown at> wrote in message news:<cmar2t$2dl6$1 at>...
> Hello: 
> I'm setting up a local caching DNS server on a Windows network 
> using the example files from 
> They are similar to, but a bit more complex than the caching example 
> in the bind documentation. I have setup other DNS servers that actually 
> serve multiple domains, but this is my first one that is CACHING ONLY. 
> It IS working. I can enter it as the ONLY DNS server in the network 
> properties of the Windows workstations, and they can still resolve 
> names using nslookup and web surfing, but the problem is when I 
> add secondary name servers, and test with nslookup. 
> In this case, with my new local caching DNS as primary and the ISP's 
> DNS as secondary (in case mine goes down) when I try to verify 
> using nslookup at the windows workstations, they come back with 
> and error that they can't find the name of my local DNS then proceed 
> to use the secondary DNS from the ISP. Here is the nslookup output:
> c:\>nslookup
> *** Can't find server name for address Non-existent domain
> Default Server:
> Address:
> >
> So it looks like the resolver function on the windows workstation is NOT 
> using the primary DNS because it can't find a name for it. But I'm not 
> sure about adding the its name to a zone file, because the company's 
> domain and name servers are hosted offsite, and I don't think I want to 
> put the internal address of a name server on out there. 
> Should I just make a reverse zone for that machine?

More information about the bind-users mailing list