Received: (at submit) by bugs.debian.org; 15 Feb 2001 00:52:06 +0000
From doogie@brainfood.com Wed Feb 14 18:52:06 2001
Return-path: <doogie@brainfood.com>
Received: from www3.brainfood.com (brainfood.com) [::ffff:216.234.231.102] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 14TCeU-0006e1-00; Wed, 14 Feb 2001 18:52:06 -0600
Received: (from doogie@localhost)
	by brainfood.com (8.9.3/8.9.3/Debian/0wns/U) id SAA31668
	for submit@bugs.debian.org; Wed, 14 Feb 2001 18:52:06 -0600
Date: Wed, 14 Feb 2001 18:52:06 -0600
From: doogie <doogie@brainfood.com>
To: submit@bugs.debian.org
Subject: fix for bind issue 925 incorrect(slave sends NOTIFY on startup)
Message-ID: <20010214185206.A31581@mail.novare.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
Delivered-To: submit@bugs.debian.org

Package: bind
Version: 8.2.3-0.potato.1

This version of bind includes a fix from upstream, that causes slaves to
send NOTIFY events to all other NS, when they start up.  The upstream
CHANGES mentions rfc1996 as the reason why this was done.  However, I
have read that rfc, and it only describes masters sending NOTIFYs to
slaves.

I consider this a bug.  It causes undue network load, increased logging,
more cpu usage, on both master and slave, etc.