You don't have a choice.

1) You add the zone/domain to the master, edit its parameters, including 
the NS (name server entries).

2) You add the zone/domain to the slave, pointing it to the master as the 
master.

Your secondaries will not...I repeat, not...attempt to pull a zone for 
which it is not configured.  Period.  The only way to tell the secondary 
that it is supposed to pull the domain's information and store it, is to 
add the domain into secondary's named.conf file.

On Thu, 23 May 2002, Andr� Cameron wrote:

> Please start from the beginning.  I do not want to add every domain it would
> take forever, I do not want to add a domain everytime I add one to the
> master.  I want the secondary to pull from the master and do its thing.  My
> named.conf looks like:
> 
> 
> // generated by named-bootconf.pl
> 
> options {
>         directory "/var/named";
>         /*
>          * If there is a firewall between you and nameservers you want
>          * to talk to, you might need to uncomment the query-source
>          * directive below.  Previous versions of BIND always asked
>          * questions using port 53, but BIND 8.1 uses an unprivileged
>          * port by default.
>          */
>         // query-source address * port 53;
> };
> 
> //
> // a caching only nameserver config
> //
> zone "." IN {
>         type hint;
>         file "named.ca";
> };
> 
> zone "localhost" IN {
>         type master;
>         file "localhost.zone";
>         allow-update { none; };
> };
> 
> zone "0.0.127.in-addr.arpa" IN {
>         type master;
>         file "named.local";
>         allow-update { none; };
> };
> key "key" {
>         algorithm hmac-md5;
>         secret
> "UzsPpktSFxACyqDBNQYwEHNzKSaAtJUJxtzQOqhML0RhITGRQxETRMadQrpG";
> };
> 
> 
> Please tell me what I have to do;)
> 
> Regards,
> Andr� Cameron
> ԿԬ
> ----- Original Message -----
> From: "Mike Burger" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, May 23, 2002 10:32 AM
> Subject: Re: DNS BIND 9 Help Please
> 
> 
> > I gave it to you a while ago:
> >
> > zone "domain.name.com" {
> > type slave;
> > masters {
> > xxx.xxx.xxx.xxx;
> > file "domain.com";
> > };
> > };
> >
> > On Thu, 23 May 2002, Andr� Cameron wrote:
> >
> > > Ok,  I must have not been clear;)  I have no clue how to setup a real
> > > secondary name server.  Could you help with step one?  How do I tell ns2
> the
> > > it is the secondary and to watch ns1 for changes?
> > >
> > > Do I change:
> > > zone "localhost" IN {
> > >         type slave;
> > >         file "localhost.zone";
> > >         allow-update { none; };
> > > };
> >
> >
> >
> > _______________________________________________
> > 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

Reply via email to