From owner-freebsd-hackers@FreeBSD.ORG Tue Jul 10 07:35:21 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 79A97106566C for ; Tue, 10 Jul 2012 07:35:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 123D3155614; Tue, 10 Jul 2012 07:35:21 +0000 (UTC) Message-ID: <4FFBDB38.3010008@FreeBSD.org> Date: Tue, 10 Jul 2012 00:35:20 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Mike Meyer References: <89AB703D-E075-4AAC-AC1B-B358CC4E4E7F@lists.zabbadoz.net> <4FF8C3A1.9080805@FreeBSD.org> <0AFE3C4A-22DB-4134-949F-4D05BBFC4C6C@lists.zabbadoz.net> <4FF8CA35.7040209@FreeBSD.org> <4FF952FB.10200@FreeBSD.org> <4FFACB51.90001@brodnik.org> <20120709204749.GA88274@server.rulingia.com> <4FFB447F.9020001@FreeBSD.org> <20120710024605.GA90875@server.rulingia.com> <4FFBD5D0.8020306@FreeBSD.org> <20120710032803.55d30a7d@bhuda.mired.org> In-Reply-To: <20120710032803.55d30a7d@bhuda.mired.org> X-Enigmail-Version: 1.4.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Replacing BIND with unbound 9.1 code freeze?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 07:35:21 -0000 On 07/10/2012 00:28, Mike Meyer wrote: > I suspect that dnsmasq is a lot better tool for that job than BIND I think "better" is in the eye of the beholder, particularly whether or not the "O" is either small or well-staffed enough to pre-enter hostnames into the zone files. That said, dnsmasq is a great tool, especially if you're relying on DDNS. OTOH, as anyone can see from the named.conf in the base, I believe rather strongly that a large'ish network should take responsibility for being authoritative for 1918 stuff (et al) so that they don't go out over the network. You can still do that with other solutions, but this is one area where the fact that BIND can do both is a feature. Doug -- Change is hard.