secondary name server question

[Kevin Darcy]

Techdog wrote:

> A newby question here I am sure...
>
> I have a primary and a secondary name server. I have been adding domains to
> the primary, and in the NAMED.BOOT file I list each domain as follows:
>
> primary domainname.com domainname.db
>
> I created a domainname.db file with the appropriate DNS information and the
> primary works fine. In the domainname.db file I tell it the name of the
> secondary name server.

You should really be using BIND 8 or BIND 9, which have "named.conf" instead of
"named.boot" configuration files...

> My questions is this: Does the primary server automatically send info to the
> secondary for the domain, or do I have to modify the NAMED.BOOT and create
> the domainname.db file on the secondary manually? What information do I have
> to put in the domainname.db on the secondary server, and what is posted
> there by the primary? I am assuming that when changes are made to the
> primary and the serial number is incremented, that this information is sent
> to the secondary automatically.... is that correct, or do I have to post all
> changes manually to the secondary server?

You need to manually configure the slave to know that it's a slave for the
zone, who the master is, and what filename to use for storing the replicated
zone. Once you do that, though, then changes will replicate automatically. You
don't even need to create the zone file; that will be done automatically. Slave
configuration requires a "secondary" directive in named.boot, or in named.conf,
a "zone" definition specifying "type slave".


- Kevin