From owner-freebsd-questions@FreeBSD.ORG Fri Dec 31 15:08:52 2004 Return-Path: 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 2C85C16A4CE for ; Fri, 31 Dec 2004 15:08:52 +0000 (GMT) Received: from kheops.speedy.net.pe (kheops.speedy.net.pe [200.48.172.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6E3D43D2D for ; Fri, 31 Dec 2004 15:08:51 +0000 (GMT) (envelope-from rcc@speedy.net.pe) Received: from elcsa30102 (unknown [10.226.252.102]) by kheops.speedy.net.pe (Postfix) with ESMTP id EDEC8263E0 for ; Fri, 31 Dec 2004 10:10:51 -0500 (PET) Message-ID: <008101c4ef4a$8b89f8b0$66fce20a@int.tp.com.pe> From: "Richard Cotrina" To: References: <6.2.0.14.2.20041231065928.00be6bc8@cheyenne.wixb.com> Date: Fri, 31 Dec 2004 10:07:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Subject: Re: 9.3.0 on FreeBSD 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 15:08:52 -0000 Is there any reason for not using bind 9.3.0 that comes with FreeBSD 5.3 ? It can be run chrooted with the same flags you are using. Regarding your question, I suposse your master server can't connect to your slaver server on port tcp 53 which is used for transfer zones and master-slave notifications because of some packet filter. Do you have any tcp-wrapper, ipfw or ipf rules that may be blocking the establishment of tcp session on port 53 ? ----- Original Message ----- From: "J.D. Bronson" To: Cc: Sent: Friday, December 31, 2004 8:04 AM Subject: 9.3.0 on FreeBSD 5.3 > It compiles fine and runs fine...but I noticed an odd thing. > > When the MASTER DNS server boots up, it fails to send notifies > to the SLAVES: > > 31-Dec-2004 06:51:33.207 zone domain.com/IN/external: notify to 1.1.1.1#53: > retries exceeded > > (tons of them..each referring to each of my domains or zones) > > None of the slaves ever see the NOTIFY. > > ..here is the odd part: > > If I kill off named (after boot is all done)...then launch it again, > the SLAVES now receive the NOTIFYs. > > So its *only* during the boot-up sequence that I am seeing this. > > Bind 9.3.0 starts in the SAME way as the OEM version that comes with > FREEBSD 5.3 with 2 exceptions. > > 1. I run it chrooted to /var/named > 2. In rc.conf, I simply specify my new compiled binary > and launch it as such: > > named_enable="YES" > named_program="/usr/local/sbin/named" > named_flags="-t /var/named -u named" > > Anyone have ANY insight on this? >