excessive notify traffic (8.2.3)

[Nick Simicich]

At 01:11 PM 3/7/2001 +1100, Mark.Andrews at nominum.com wrote:
>
>	What errors are you logging.  A NOTIFY is triggered by loading
>	the zone or the heartbeat timer going off and the zone being
>	a dialup zone.

None of the above apply.  The notifies are coming way too fast and furious for that.  Like, hundreds an hour.  Logging no errors, doing nothing but passing notifies and responses to notifies around.  All I was logging was notify sent, response to notify received, notify sent, response to notify received.  etc.  As I noted in my last message about this, I'd have all the serials in a zone matching and I'd still be getting these notify storms.

>	My bet is that you have lots of expired children of the zones
>	in question or there is a load failures on a child zone causing
>	the server to reload the parent zone.

How much do you want to bet?  You lose, in my case. I was getting these on squawk.com which has no child zones.   This is a bug.  I was getting them on labed.com which has no child zones, had all the serials matching, I was getting no load messages or other error messages from my servers and I was still sending out notifies over and over and over again - they are not defined as dialup zones on the master.

>	Mark
>> 
>> 
>> 
>> At 11:30 AM 3/6/2001 -0600, Craig R. Bina wrote:
>> >
>> >I recently migrated our DNS from an old SunOS box to a new
>> >Debian box.  All seems to work fine, except that the primary
>> >sends out NOTIFY messages about every 10 seconds for the 3
>> >zones for which it is master.  Any ideas what might be wrong?
>> 
>> I had the same experience upgrading to 8.2.3.  If I had two servers, a maste
>> r and a slave, and they both ran 8.2.3, the notify traffic eventually died o
>> ff.
>> 
>> If I had some offsite slaves, another master where the data was manually syn
>> ched, etc., the notify traffic just kept on coming.  If there was a server w
>> hich wasn't taking the notifies and hadn't yet gotten a matching serial but 
>> which was responding to the notifies it seems to triggernever ending notifie
>> s.  But even when serials matched, there would still be notifys.
>> 
>> This got to the point where there were thousands and thousands of logged mes
>> sages regarding notify.
>> 
>> Something is seriously wrong with notify, what I did was set "notify no" in 
>> the affected domains.
>> 
>> If there is a reason for the notifies, like some soft of mismatch triggering
>>  another notify cycle, the messages don't give the information you need to f
>> ix it.
>> 
>> I consider this a serious problem.  I wish I knew what to do about it.

--
We will fight for bovine freedom, And hold our large heads high.
We will run free, with the buffalo or die! Cows with Guns.
 - Dana Lyons, Cows With Guns
Nick Simicich mailto:njs at scifi.squawk.com
http://scifi.squawk.com/njs.html -- Stop by and Light Up The World!