|
That means two things: 1)
The DNS slave has to be configured manually, since I can’t find cookbooks that report this. I’ve certainly done that, but I’d like to have a recipe
for it. 2)
The masters and slaves can’t back up each other for zones that each of them may configure through some local configuration settings. For example,
if I’ve got two production environments, one for web servers, and one for data base severs, and they have two chef servers,, and one chef server is in “db.example.com” and the other is in “web.example.com”, it might be really handy to have them swap master
and slave relationships for servers they manage. That way, each of them can populate its DNS with its own chef clients, but both sets of clients can use either DNS server and gain some backup. So I’m hoping someone else has already writing recipes and cookbooks for DNS slave relationships. -- From: Pete Cheslock [mailto:
You could try to setup a secondary DNS server and use zone transfers to keep the master (kept up to date with chef) and the slaves up to date with the master? On Wed, Sep 4, 2013 at 1:59 PM, Kadel-Garcia, Nico <
" target="_blank">
> wrote: I’m looking at some DNS masters configured with chef, using the built-in tools to audit for chef
clients and populate DNS zones with them. So far, so good. The DNS master works well. But I’d really like to set up a DNS slave with chef, for when the DNS server needs restarting or
OS upgrades. Unfortnately, I don’t seen any hooks for DNS slaves in the bind9 cookbook. And ideally, I’d like to have two chef servers, one for one DNS domain, and another for another DNS domain, and allow them to be masters and slaves for each other to provide
failover. I’d really prefer not to write one from scratch, if I can avoid it gracefully. -- |
Archive powered by MHonArc 2.6.16.