From owner-freebsd-net@FreeBSD.ORG Tue Feb 25 08:27:12 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 271D8BA4 for ; Tue, 25 Feb 2014 08:27:12 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0AE681AE7 for ; Tue, 25 Feb 2014 08:27:11 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WIDM1-00032Q-L3 for freebsd-net@freebsd.org; Tue, 25 Feb 2014 00:27:05 -0800 Date: Tue, 25 Feb 2014 00:27:05 -0800 (PST) From: Beeblebrox To: freebsd-net@freebsd.org Message-ID: <1393316825645-5888870.post@n5.nabble.com> Subject: Unbound's dnssec-keygen in FreeBSD MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2014 08:27:12 -0000 Unless I'm wrong, Unbound seems to natively support "dnssec-keygen" (from this document) http://www.nlnetlabs.nl/publications/dnssec_howto/#x1-620009.2.1 I have Unbound built and running, but there is no dnssec-keygen on the system. Was this not ported to FreeBSD's version of Unbound? I suppose I have to install dns/bind99 if I need dnssec-keygen? ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Unbound-s-dnssec-keygen-in-FreeBSD-tp5888870.html Sent from the freebsd-net mailing list archive at Nabble.com.