A question ...

[Barry Margolin]

In article <94kcj2$t5f at pub3.rc.vix.com>,
Francesco Ratto  <frankie at yond.it> wrote:
>
>Barry Margolin kindly wrote ...
>
>> On the secondary server, configure the slave zone in its named.conf file
>> and then do "rndc reconfig" to make it learn about the new zone.  It will
>> transfer the zone automatically.
>
>ok I tried to configure only the secondary named.conf with 
>the datas about the new domain i set a refresh time of 5 minutes 
>and the new domain was taken by the secondary .......good
>
>the rndc doesn't have  a reconfig option ... what do you mean ?

ndc has this option, so I assumed rndc also did.  If reconfig isn't
available, use reload.

>now .. Does exist tools that allow me to
>
>    have a copy of secondary named.conf on the primary (the initial one)
>    automatically update the copy with the new domains eventually
>    added  on the primary named.conf (with the modifications required)
>    transfer the secondary named.conf to the secondary server 

It shouldn't be difficult to write a Perl or awk script that creates a
secondary named.conf file by reading the primary file, and then use scp to
copy it to the secondary server.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, 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.