secoundary ns - not authoritative

[David Botham]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]
> On Behalf Of Alexander Newald
> Sent: Thursday, August 15, 2002 3:38 PM
> To: comp-protocols-dns-bind at isc.org
> Subject: Re: secoundary ns - not authoritative
> 
> "Gaebel Michael (MGI DCS)" <Gaebel at mgi.de> schrieb im Newsbeitrag
> news:ajgme9$8hq3$1 at isrv4.isc.org...
> >
> > Hello you have to say, that he is a scondary:
> >
> > zone "example.com" IN {
> >   type slave;
> >   file "filename
> >   masters port 53 {
> >     master-ip-adress
> >   };
> > };
> >
> > -----Original Message-----
> > From: Alexander Newald [mailto:alexander at newald.de]
> > Sent: Thursday, August 15, 2002 4:48 PM
> > To: comp-protocols-dns-bind at isc.org
> > Subject: secoundary ns - not authoritative
> 
> [question about 2nd ns and not authoritative]
> 
> So it is not possible to tell the secoundary ns that it should be
> authoritative for all domains that are send by zone transfers from
> the primary ns without createing an entry in the named.conf for
> each zone?  
> 
You are mis-understanding the slave / master relationship.  Masters
do not send a zone transfer to the slaves.  Slaves pull a zone
transfer from the master.  In other words, upon start, a name server
reads it named.conf file.  For each zone listed as type slave, the
name server contacts the IP(s) listed in the "masters" list and
attempts to pull the zone via a zone transfer.  A master never forces
(sends) a zone transfer to a slave, it simply allows permitted slaves
to pull zones via zone transfers.

Master will, however, send NOTIFY messages to slaves when a zone is
reloaded.  If a the slave(s) have the zone loaded, the slave will set
the zone's Refresh interval to zero, check the serial number on the
master, and if it is larger that the current serial number, the slave
will pull a zone transfer of the zone's contents.

Dave...




> Alexander Newald
> 


-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4

iQA/AwUBPV0LaFq85iiiMQ4EEQK3XACgmE2xhgMhHqg5/j/t2ZrRT/8kbwIAnRld
nZ5EH4mujn10ZjhITZMbNlYQ
=CB+j
-----END PGP SIGNATURE-----