IXFR and Notify speed
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Tue Sep 24 00:12:32 UTC 2002
>
>
>
> Is there a log kept to find out a failed NOTIFY attempt
> by the master server?
debug level 3.
dns_zone_log(zone, ISC_LOG_DEBUG(3),
"refused notify from non-master: %s", fromtext);
> All of the NS records are resolvable and the secondary
> that would request the IXFR is one of the NS records.
>
> The secondary is refreshed when I do a "rndc refresh"
> but other than that it is waiting for the refresh time set
> in the SOA.
>
>
>
>
>
> On Tue, 24 Sep 2002 Mark.Andrews at isc.org wrote:
>
> >
> > >
> > >
> > > I have NS records for all of the nameservers.
> > > All namservers are 9.2.2rc1 or 9.2.1
> > >
> > > The master nameserver has: (even tough it's on by default)
> > > provide-ixfr yes;
> > >
> > > The slave nameserver has: (even though it's on by default)
> > > request-ixfr yes;
> > >
> > > Yet, it is taking very long for the slave servers to be updated.
> > > Is there something else that needs to be done or is this a bug?
> > >
> > > Thanks for any help.
> >
> > Firstly the notify messages have to come from the correct
> > IP addresses. See notify-source and allow-notify.
> >
> > Secondly the master has to be able to resolve the addresses
> > of the slave nameservers.
> >
> > Also check firewall settings.
> >
> > Mark
> > --
> > Mark Andrews, Internet Software Consortium
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
> >
>
>
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list