[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Colo says need scond server



 Frank Cubillos <cubillos@xxxxxxxxxxxxxxxxxx> wrote


> This is incorrect isn't it?
> "Also, the cobalt server can be setup as a Name Server and we know how to do
> this.  However, unless you wish to get two RAQ servers and setup DNS on both
> of them, you wil still need to use our DNS server as a backup DNS server.
> Which means that even though you enter the DNS into your RAQ server, it will
> need to be on ours as well to serve as a backup."
>

The secondary should be setup as a slave nameserver. Meaning that you only have
to maintain the records on the Primary (Master).
You do not have to worry about synchronizing the files, the slaves do that for
you. Of course the changes do not happen instantly, the slave polls to see if it
is current, the polling interval is based on the "refresh" setting in the SOA
record, expressed in seconds, usually from 3 to 12 hours. The Slave will query
the Masters serial number if the number has changed it will reload the zone
files over the network. Therefore when the Master DB is updated the serial
number is to be incremented. I do not know if Cobalt GUI does that but it
should!
Get your ISP to set his nameserver up as a slave!