Master <--> slave named.conf "auto-generation"
Baird, Josh
jbaird at follett.com
Thu Mar 13 13:24:27 UTC 2008
No functionality for this exists in BIND. The way that I have accomplished this in the past is to keep a separate named.conf (ie, named-slave.conf) on the master and use a simple script that scp'd the named.conf over to all of the slaves, used sudo via ssh to copy the named.conf to the proper location and then did a "rndc reconfig" (better than using "rndc reload" if all you are doing is modifying named.conf).
This seems to work fine, and I still use this method for my external environment.
Josh
-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf Of bsd
Sent: Thursday, March 13, 2008 3:41 AM
To: bind-users at isc.org
Subject: Master <--> slave named.conf "auto-generation"
Hello,
I would like to know if there is a way, whenever a new zone definition
is added to the primary master server, to have the slaves
automatically configure themselves with matching slave-zone definitions?
If not - what are people currently using to acomplish this task?
Have you got any good script that could help me achieve that in an
"elegant" way?
What are the best path to achieve this knowing that I could have
master and slave file generated on one server (the master), how would
you handle the propagation of the named.conf (slave) file and signal
(rndc reload) and the slave?
Any other advise / experience / experiment are welcome.
Thx.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Gregober ---> PGP ID --> 0x1BA3C2FD
bsd @at@ todoo.biz
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
P "Please consider your environmental responsibility before printing
this e-mail"
More information about the bind-users
mailing list