From owner-freebsd-questions Thu Jul 20 10:21:20 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 587EA37B685 for ; Thu, 20 Jul 2000 10:21:14 -0700 (PDT) (envelope-from gabriel_ambuehl@buz.ch) Received: (qmail 515 invoked from network); 20 Jul 2000 17:21:24 -0000 Received: from unknown (HELO 10.2.2.100) (62.2.98.229) by ns1.root-servers.ch with SMTP; 20 Jul 2000 17:21:24 -0000 Date: Thu, 20 Jul 2000 19:22:04 +0200 From: Gabriel Ambuehl X-Mailer: The Bat! (v1.44) UNREG / CD5BF9353B3B7091 Organization: BUZ Internet Services X-Priority: 3 (Normal) Message-ID: <1854804678.20000720192204@buz.ch> To: questions@FreeBSD.org, isp@FreeBSD.ORG Subject: named broken? 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 Hello, I cvsupped my development box at about 13:00 GMT and did a make world afterwards. I now had to reboot it and named, which has got exactly one slave zone and one dummy zone for the LAN, began to bomb the primary (which is colocated elsewheree) with named-xfers to a point, where my 512kbit connection wasn't of real use anymore (ssh with about two chars/s...). Has anyone a idea what's happening here? 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). Best regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message