On Thu, Mar 31, 2011 at 03:49:19PM -0400, Elliot Peele wrote: > There is a named running on fdev, but I'm not sure if it is being used. The > whois records for foresightlinux.org point at Ken's dns servers.
fdev is the master; ken and I run the two slaves. The glue records point to the slaves, and the master is accessible only from the slaves. This means that anyone who can configure named on fdev is able to modify foresight dns, but fdev's bind isn't publicly exposed in a general sense. But modifications on fdev and restarting named cause immediate notifies to go to the slaves to which the glue records point. (Separately, I'm doing automated nightly offsite backups of important data from the fdev cluster, including named configuration. This also includes full confluence and jira dumps. I'll have to turn that off for the weekend.) _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
