From owner-freebsd-questions@FreeBSD.ORG Wed Feb 8 16:45:52 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3855D16A420 for ; Wed, 8 Feb 2006 16:45:52 +0000 (GMT) (envelope-from tim@tetro.net) Received: from uts.tetro.net (uts.tetro.net [192.83.249.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0849243D46 for ; Wed, 8 Feb 2006 16:45:51 +0000 (GMT) (envelope-from tim@tetro.net) Received: from tim by uts.tetro.net with local (Exim 4.50) id 1F6sRs-0006Uf-64; Wed, 08 Feb 2006 08:45:44 -0800 Date: Wed, 8 Feb 2006 08:45:44 -0800 To: jhall@vandaliamo.net Message-ID: <20060208164544.GB24684@tetro.net> References: <4822.12.170.206.13.1139402702.squirrel@admintool.trueband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4822.12.170.206.13.1139402702.squirrel@admintool.trueband.net> User-Agent: Mutt/1.5.9i From: Tim Utschig Cc: freebsd-questions@freebsd.org Subject: Re: BIND zone transfers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 16:45:52 -0000 On Wed, Feb 08, 2006 at 12:45:02PM -0000, jhall@vandaliamo.net wrote: > Under FreeBSD 4.8 BIND was making zone transfers normally. In my network, > Windows 2000 is the master and bind is the salve. Recently, the server > was upgraded to FreeBSD 6.0, and suddenly BIND stopped making zone > transfers, except for the first zone, which is transferred just as it > should be. Zone transfers are taking place from a W2K server. I am > seeing this problem with BIND 9.3.2 and BIND 9.3.1 Saw this in the BIND FAQ, maybe it applies to your situation: Q: Zone transfers from my BIND 9 master to my Windows 2000 slave fail. Why? A: This may be caused by a bug in the Windows 2000 DNS server where DNS messages larger than 16K are not handled properly. This can be worked around by setting the option "transfer-format one-answer;". Also check whether your zone contains domain names with embedded spaces or other special characters, like "John\032Doe\213s\032Computer", since such names have been known to cause Windows 2000 slaves to incorrectly reject the zone. -- - Tim Utschig