From owner-freebsd-ports@FreeBSD.ORG Mon Nov 15 17:03:37 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CEEE16A4CE; Mon, 15 Nov 2004 17:03:37 +0000 (GMT) Received: from relay.epsb.ca (relay.epsb.ca [198.161.119.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E716D43D1D; Mon, 15 Nov 2004 17:03:36 +0000 (GMT) (envelope-from Sean.Page@epsb.ca) Received: from exchange03.epsb.ca (exchange03.epsb.ca [10.0.5.11]) by relay.epsb.ca (8.12.11/8.12.11) with ESMTP id iAFH3YQM047741; Mon, 15 Nov 2004 10:03:34 -0700 (MST) (envelope-from Sean.Page@epsb.ca) Received: by exchange03.epsb.ca with Internet Mail Service (5.5.2653.19) id <4G435TCG>; Mon, 15 Nov 2004 10:07:15 -0700 Message-ID: <1FE05C67E513D9119F31000F1F6C220742CC@EXCHANGE08> From: Sean Page To: "'Doug Barton'" Date: Mon, 15 Nov 2004 10:01:58 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain cc: "'freebsd-ports@freebsd.org'" Subject: RE: Name resolution performance in BIND9 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 17:03:37 -0000 Excellent, that has indeed done the trick. Thanks for the explanation Doug. -----Original Message----- From: Doug Barton [mailto:DougB@freebsd.org] Sent: November 14, 2004 1:08 PM To: Sean Page Cc: 'freebsd-ports@freebsd.org' Subject: Re: Name resolution performance in BIND9 On Fri, 12 Nov 2004, Sean Page wrote: > Greetings list. > > I am running versions of FreeBSD from 4.9.x to 4.10 p3. Let's say for the > sake of argument that we're dealing with FreeBSD 4.10-RELEASE-p2. I am > finding that BIND9 (installed to replace the base install of BIND) is taking > from 4-8 seconds to resolve a name that isn't cached, where the same lookup > on BIND8 will occur in less than a second. This is happening because of the way BIND 9 handles the presence of AAAA records in the glue data. May TLDs, including recently both com and net, have AAAA records now. The problem will be fixed in 9.3.1 when it is released. Meanwhile, those who have only IPv4 connectivity can solve the problem by putting -4 in their named_flags in /etc/rc.conf[.local]. HTH, Doug