From owner-freebsd-questions Thu Jul 20 11:27:49 2000 Delivered-To: freebsd-questions@freebsd.org Received: from alpha.root-servers.ch (alpha.root-servers.ch [195.49.62.125]) by hub.freebsd.org (Postfix) with SMTP id BA61837BC8F for ; Thu, 20 Jul 2000 11:27:39 -0700 (PDT) (envelope-from gabriel_ambuehl@buz.ch) Received: (qmail 992 invoked from network); 20 Jul 2000 18:27:51 -0000 Received: from unknown (HELO 10.2.2.100) (62.2.98.229) by ns1.root-servers.ch with SMTP; 20 Jul 2000 18:27:51 -0000 Date: Thu, 20 Jul 2000 20:28:32 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.44) UNREG / CD5BF9353B3B7091 Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <808792502.20000720202832@buz.ch> To: freebsd-questions@freebsd.org Subject: [SOLVED] Re: named broken? In-reply-To: <1854804678.20000720192204@buz.ch> References: <1854804678.20000720192204@buz.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thursday, July 20, 2000, 7:22:04 PM, I wrote: > If I comment the zone in named.conf out, everything works as usual. > During the reboot, named stated that the slave zone did timeout > but from my understanding, a single named-xfer would be enough > to get that solved (and bombing the primary dns is surely not required > anyway). For some reasons (I'm VERY sure I didn't set it), /etc/namedb/s/zonefile was chflagged schg so named couldn't update it and ran amok... Removing the chflags did solve the problems. Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message