Re: [cobalt-developers] DNS Set-up

["Jamie Rossi" <jamie@xxxxxxxxx>]

You can always set both machines up as primary dns servers, and sync the
files between the two machines from named.

The problem is that the record type for a secondary is different to a
primary zone, and therefre they cannot be done automatically. I have worked
for some very large ISPs and they always set up with the "secondary" DNS
actually being a master server with master zones on, and syncing the .db
files between two boxes.

Cheers

Jamie
----- Original Message -----
From: "Gerald Waugh" <gerald@xxxxxxxxx>
To: <cobalt-developers@xxxxxxxxxxxxxxx>
Sent: Saturday, May 26, 2001 4:18 AM
Subject: Re: [cobalt-developers] DNS Set-up


> > Is this not a developers list? The questions I been asking is if
somebody
> > know or has advise on how to I can go about programming a solution were
I
> > can have my slaves auto-update without creating the enties in the
secondary
> > as per cobalts advise.
> >
> Actually I responded to the wrong post, you have my apologies.
> The only solution I can think of is to use rsync. I use rsync for
synchronizing
> files
> on several servers for other purposes. There is a way to get rsync to
execute
> a command. You would have to create the master named.conf, and the slave
> named.conf on the master, then sync the slaves to the revised slave
named.conf,
> and execute ndc reload.
> The master would be the rsync client and the slaves would run rsync
daemon.
> Then when the zone files were updated the client would run a script to
sync the
> file to each of the slaves, and issue the command to execute ndc reload.
> Gerald
>
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>
>