Secondary sending notify to itself
Loomis, Rip
GILBERT.R.LOOMIS at saic.com
Wed Jun 19 20:52:17 UTC 2002
Richard--
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.
--Rip
> -----Original Message-----
> From: Richard Caissie (EUD) [mailto:Richard.Caissie at am1.ericsson.se]
> Sent: Wednesday, 19 June, 2002 15:09
> To: bind9-workers at isc.org
> 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 named.run file. Note the slave server is
> at address 10.5.0.32.
>
> Jun 19 11:50:02.272 zone qatest.com/IN: notify response from
> 10.5.0.32#53: REFUSED
>
> thanks,
>
> Rich Caissie
>
>
>
More information about the bind-workers
mailing list