From owner-freebsd-questions Sun Dec 30 6: 3:24 2001 Delivered-To: freebsd-questions@freebsd.org Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by hub.freebsd.org (Postfix) with ESMTP id 5FD8B37B417 for ; Sun, 30 Dec 2001 06:03:15 -0800 (PST) Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by cactus.fi.uba.ar (8.11.6/8.11.6) with ESMTP id fBUE16e51225; Sun, 30 Dec 2001 11:01:07 -0300 (ART) (envelope-from fgleiser@cactus.fi.uba.ar) Date: Sun, 30 Dec 2001 11:01:06 -0300 (ART) From: Fernando Gleiser To: Bill Moran Cc: Subject: Re: [OT] bind problems In-Reply-To: <3C2E779B.6050205@potentialtech.com> Message-ID: <20011230105415.P50812-100000@cactus.fi.uba.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 29 Dec 2001, Bill Moran wrote: > I've got a FreeBSD proxy that's supposed to be running bind as a caching nameserver, > but something is awry and I can't figure out what the Sam-Hill I goofed up. > FreeBSD 4.4-RELEASE > bind 8.2.4-REL > > I've attempted to configure named to "forward only" so that it just does all > its resolving through the upstream servers. I also have the clients > configured to use the upstream servers as backups. Apparently this caching > server is never answering any queries and the upstreams are getting all > the questions (which, obviously, defeats the purpose) Without looking at the named.conf file, we can't say whats wrong with your bind configuration. > When I run nslookup on the proxy, I get an error: > *** Can't find server name for address 127.0.0.1: No response from server > And it falls back to the secondary to answer the queries. Don't use nslookup. Again: Don't use nslookup. Use dig instead. nslookup fails miserably if you don't have the reverse zones properly configured. It tries a reverse lookup of the IP listed in the "nameserver" clause of resolv.conf and dies if fails. I don't know why someone wrote a debugging tool for DNS which needs named properly configured in the first place. Fer > /var/log/messages records the following complaint from named every time I run > nslookup: > ns_req: no address for root server > > Anyone have any ideas what's wrong here? I'd be more than happy to provide > the config files, but I didn't want to spam the list if it's something dumb that > I goofed and someone can point it out without the config files. > > -- > Bill Moran > Potential Technology > http://www.potentialtech.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message