From owner-freebsd-questions Wed Nov 24 11:33:26 1999 Delivered-To: freebsd-questions@freebsd.org Received: from athserv.otenet.gr (athserv.otenet.gr [195.170.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1CC19153DA for ; Wed, 24 Nov 1999 11:33:12 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from localhost.hell.gr (patr530-a016.otenet.gr [195.167.115.16]) by athserv.otenet.gr (8.9.3/8.9.3) with SMTP id VAA00392 for ; Wed, 24 Nov 1999 21:32:06 +0200 (EET) Received: (qmail 2279 invoked by uid 1001); 24 Nov 1999 11:51:44 -0000 To: freebsd-questions@freebsd.org Subject: Re: named going NUTZ!! UPDATE References: <389492510.943388365721.JavaMail.root@web01.pub01> From: Giorgos Keramidas Date: 24 Nov 1999 13:51:44 +0200 In-Reply-To: Pedro Leitao's message of "Tue, 23 Nov 1999 15:19:25 -0500 (EST)" Message-ID: <864secm7jj.fsf@localhost.hell.gr> Lines: 16 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pedro Leitao writes: > It turns out that the problem is coming from my secondary DNS server. The > secondary was doing exactly the same. As soon as I kill named on the > secondary, the load went down to 0.00 0.00 0.00 > > Why would this happen? Yep, look for those expiry lines. Every time a secondary's zones expire, they're updated from the primary name server. Expiring too late means you might not always have the very-latest changes in the records. Expiring too early means that a lot of cpu time and bandwidth is wasted. -- Giorgos Keramidas, "What we have to learn to do, we learn by doing." [Aristotle] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message