Secondary sending notify to itself

Richard Caissie (EUD) Richard.Caissie at
Wed Jun 19 21:55:32 UTC 2002


The secondary has only the primary in the masters {} list and there
are NS records for both secondary and primary and no more.  So my guess is 
that it is prompted to send a notify to itself because of its own NS record.

best regards,

-----Original Message-----
From: Loomis, Rip [mailto:GILBERT.R.LOOMIS at]
Sent: Wednesday, June 19, 2002 4:52 PM
To: 'Richard Caissie (EUD)'
Cc: bind9-workers at
Subject: RE: Secondary sending notify to itself

Does the system list itself in the masters{} stanza
or an also-notify{} stanza for that zone?  If not, then
I would guess it's a real "non-feature" related to
proxying dynamic updates back up to the "real" master
for the zone.

> -----Original Message-----
> From: Richard Caissie (EUD) [mailto:Richard.Caissie at]
> Sent: Wednesday, 19 June, 2002 15:09
> To: bind9-workers at
> Subject: Secondary sending notify to itself
> Hi Folks,
> Is there a reason that a BIND 9 slave server sends a notify 
> to itself after receiving an IXFR?
> I got this from the file.  Note the slave server is 
> at address
> Jun 19 11:50:02.272 zone notify response from 
> thanks,
> Rich Caissie

More information about the bind-workers mailing list