From owner-freebsd-questions Fri Apr 6 8:47:58 2001 Delivered-To: freebsd-questions@freebsd.org Received: from tethys.valhalla.net (tethys.valhalla.net [195.26.32.112]) by hub.freebsd.org (Postfix) with ESMTP id C3C7637B422 for ; Fri, 6 Apr 2001 08:47:55 -0700 (PDT) (envelope-from mark@tethys.valhalla.net) Received: by tethys.valhalla.net (Postfix, from userid 500) id 5958732E7E; Fri, 6 Apr 2001 16:47:54 +0100 (BST) Date: Fri, 6 Apr 2001 16:47:54 +0100 From: Mark Drayton To: freebsd-questions@freebsd.org Subject: Nameserver resolv.conf Message-ID: <20010406164754.A26979@tethys.valhalla.net> Mail-Followup-To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi We've got a pair of nameservers which are authoritative for around 1700 domains which were also the resolvers for all our machines and clients (we're an ISP). I set up a FreeBSD machine to work as a caching only nameserver to act as a resolver for our client and staff machines to try to remove the load on our main servers. Should I set the first nameserver line in resolv.conf on our two authoritative nameservers to the new caching only server? Currently the preferred resolver is the machine itself. Ideally I'd like to make the two authoritative servers not answer recursive queries, but there are more old machines using them as resolvers than I could ever find. The two authoritative nameservers are also mail relays so they're doing a lot of lookups. It would seem better to point them at a machine that doesn't lose it's cache every time we change the zone data. Cheers, -- Mark Drayton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message