# [EMAIL PROTECTED] / 2002-10-14 20:02:11 +0100: > I've got named configured as a caching nameserver in a sandbox on my > gateway as per the Handbook. However when I run nslookup on other > machines on my network, I get this: > # nslookup <lan box> > Server: <upstream NS> > Address: upstream NS IP> > > *** <upstream NS> can't find <lan box>: Non-existent host/domain > #
I can't really help you with this one (I use different software for DNS), and I see others already tried to guess what you were doing, but you might want to read this anyway: http://homepages.tesco.net./~J.deBoynePollard/FGA/dont-obscure-your-dns-data.html and why you should never use nslookup(1): http://www.faqts.com./knowledge_base/view.phtml/aid/9287/fid/699 http://cr.yp.to/djbdns/faq/tinydns.html#nslookup http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-daft-error-message.html > I'm thinking that I can't resolve any other hosts on my network because > I've not got entries for them in a zone file, but then the handbook says > that to create a caching nameserver: > > "A caching name server is a name server that is not authoritative for > any zones. It simply asks queries of its own, and remembers them for > later use. To set one up, just configure the name server as usual, > omitting any inclusions of zones." > > So, am I missing something here. I might well be mistaken in my > understanding of exactly *what* a caching nameserver is supposed to do. http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-server-roles.html -- If you cc me or take the list(s) out completely I'll most likely ignore your message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message