newbie Bind 8.2.3 on solaris question

[Kevin Darcy]

I'm not sure what distinction you're trying to make between "secondary" and
"slave" in this context.

It should be as simple as just changing the zone definitions from type
master to type slave and telling the slaves who the masters for the zone
are (in the "masters" statement). See the docs for the full syntax. Delete
the (former) master files, reload the nameserver, and the new slave should
copy the zone data from the master and store it in a backup file.

If you have allow-transfer restrictions on the master(s), of course, you'll
probably have to modify them. And if you want to get fancy with TSIG, IXFR,
etc. that will also require some additional configuration.

You shouldn't have to change any zone records when reconfiguring a master
to a slave or _vice_versa_, although of course you must do so if you are
changing a "stealth" slave (one that other nameservers don't know to ask
about names in the zone) to a "registered" slave (one that other
nameservers know about because they are in the delegation and/or published
NS records for the zone) or _vice_versa_. If you're doing Dynamic Update,
you may also need to change the SOA.MNAME to reflect the real master.


- Kevin

jrs at enteract.com wrote:

> Hi,
>
> I'm running solaris 7 and bind 8.2.3 on multiple machines.  They are all
> acting as masters for the same address space.  What I want to do is
> convert a few to secondary and a few two slaves.
>
> 1.  What do I have to change (zone records etc) in order for it to be a
> secondary or slave server and recieve updates via zone updates etc.
>
> Thanks for the help
>
> JRS