From owner-freebsd-current@FreeBSD.ORG Sat Jun 7 13:31:22 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC06B37B401; Sat, 7 Jun 2003 13:31:22 -0700 (PDT) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00BAA43F93; Sat, 7 Jun 2003 13:31:20 -0700 (PDT) (envelope-from netch@lucky.net) Received: from netch@localhost [127.0.0.1] (netch@localhost [127.0.0.1]) by burka.carrier.kiev.ua with ESMTP id h57KVDY2024211; Sat, 7 Jun 2003 23:31:14 +0300 (EEST) (envelope-from netch@burka.carrier.kiev.ua) Received: (from netch@localhost) by burka.carrier.kiev.ua (8.12.8p1/8.12.8/Submit) id h57KVBCk024208; Sat, 7 Jun 2003 23:31:11 +0300 (EEST) (envelope-from netch) Date: Sat, 7 Jun 2003 23:31:11 +0300 From: Valentin Nechayev To: Doug Barton Message-ID: <20030607203111.GN83663@lucky.net> References: <20030605235254.W5414@znfgre.qbhto.arg> <20030606024813.Y5414@znfgre.qbhto.arg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030606024813.Y5414@znfgre.qbhto.arg> X-42: On X-Verify-Sender: verified cc: freebsd-current@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: Way forward with BIND 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: netch@lucky.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jun 2003 20:31:23 -0000 Fri, Jun 06, 2003 at 03:01:02, DougB wrote about "Re: Way forward with BIND 8": > >> FYI, for those wondering why I'm not considering BIND 9 for import, please > >> see http://people.freebsd.org/~dougb/whybind8.html Among other things: standard resolver is waaay(tm) old. Even keeping with BIND8, it is old. At least, it isn't thread-safe; this is too ugly for 5.*. Unlike IRS code (gethostby*()), its upgrading to thread safe version is conceptually easy. I've created and successfully tested patch to upgrade it to 8.3.4 version, losing only res_*update() and RES_INSECURE*; it was very simple, and a person more informed in its specifics including KAME hacks can do it better. (ftp://segfault.kiev.ua/pub/freebsd/newresolv for someone wanting to see it. I should repeast that this attempt may be too lame and forgetting some principal moments, but it was successfully tested on real load for a long time.) -netch-