Ok...I think we're at a minor impasse, here.
The master has to have the names of the secondary servers in the domain's
zone file.
The master will then notify the secondaries (slaves) that there is an
update.
Assuming that you've set up the named.conf to tell the secondaries
(slaves) that they're slave servers for the domain in question, then this
is what happens.
1) you update the records and serial number on the master's zone file for
that domain.
2) you "service named restart" to restart the name server
3) upon restart, named will notice that there is a change in a particular
domain's zone file
4) the master will then notify the other name servers listed in that
domain's zone file...these other name servers should be your slave
servers.
5) Upon receiving the notify message from the master, the slaves should
automatically retrieve the updated zone file.
Does that clear it up for you>
On Thu, 23 May 2002, Andr� Cameron wrote:
> So there is no way for the slave to pull the records directly from the
> master? I have to manually add all secondary names?
>
> Regards,
> Andr� Cameron
> ԿԬ
> ----- Original Message -----
> From: "Mike Burger" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 23, 2002 1:34 AM
> Subject: Re: DNS BIND 9 Help Please
>
>
> > If I'm understanding you, correctly, you can't.
> >
> > The slave has to know that it is a slave for that domain, and the only way
> > to do so is to tell it so in /etc/named.conf.
> >
> > You also must tell the primary that the slave exists, by placing an NS
> > record in the domain's zone file, pointing at the secondary/slave...for
> > two reasons:
> >
> > 1) The primary will be telling the world that the slave is also
> > authoritative for the domain, in spite of what the NIC record says (do a
> > whois on your domain, and then a "dig in ns" on your domain...sometimes,
> > you get different infor in the two results).
> >
> > 2) By telling the primary, in its zone file, what its secondary servers
> > are, you allow the primary to "notify" the secondary/slave that there's
> > been an update in the zone, and then the secondary/slave will pull the new
> > zone file down, on its own.
> >
> > If sites were able to be told, from remote, that suddenly they were to be
> > a secondary name server, without someone actually logging in, modifying
> > the configuration, and telling it it was secondary, there could and
> > probably would be rampant abuse.
> >
> > If it were possible to do so (and I'm glad it's not), then I could simply
> > point all my domains at your servers, telling them that they're now
> > slaves/secondary name servers, and I could point a ton of traffic at your
> > systems...that wouldn't be very friendly, now, would it? <G>
> >
> > On Wed, 22 May 2002, Andr� Cameron wrote:
> >
> > > > zone "domain.name.com" {
> > > > type slave;
> > > > masters {
> > > > xxx.xxx.xxx.xxx;
> > > > };
> > > > };
> > >
> > > How can I get the slave to automatically pull the zone files from the
> master
> > > verses me manually adding the slave record every time I add a domain?
> >
> >
> >
> > _______________________________________________
> > Seawolf-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/seawolf-list
> >
>
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
>
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
