Issues with DNS NOTIFY using BIND 9.1.3
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Tue Aug 28 23:23:52 UTC 2001
> Thanks for the reply...
>
> The slave is listed in the NS record. I did not see a need to list the slave
> in both places. One or the other should work ...correct????
>
> -----Original Message-----
> From: Barry Margolin [mailto:barmar at genuity.net]
> Sent: Tuesday, August 28, 2001 3:39 PM
> To: comp-protocols-dns-bind at moderators.isc.org
> Subject: Re: Issues with DNS NOTIFY using BIND 9.1.3
>
>
> In article <9mgr2k$3b5 at pub3.rc.vix.com>,
> Vinson Armstead - PA <Vinson_Armstead at GMACM.COM> wrote:
> >After making a change to the zone files on my master server I restart BIND
> >(kill -HUP ???). I check my slave server it does not seem to have received
> >the DNS NOTIFY sent from the master. The zone files on the secondary are
> not
> >updated and do not update until the TTL expires or I restart BIND (kill
> >-HUP).
>
> Is the slave listed in the NS records or also-notify lists of the zones?
> That's how the master determines where to send notifies to.
>
> --
> Barry Margolin, barmar at genuity.net
> Genuity, Woburn, MA
> *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
> Please DON'T copy followups to me -- I'll assume it wasn't posted to the
> group.
>
>
>
It could also be that:
* the master is sending the NOTIFY messages from the "wrong" IP
address.
* a firewall is stopping the NOTIFIES getting through.
* The master is not being allowed to look up the address of the
slave or is having problems looking up the address of the slave.
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
More information about the bind-users
mailing list