On Dec 20, 2011, at 5:11 AM, Vincent Jorgensen email@example.com wrote:
I’m an avid chef user and recent convert to the chef way and ruby way. I’m a frequent reader of the list, but this is my first post, so if this is out of line for this list, let me know and I’ll post my question elsewhere.
I’m looking for a good cookbook for use with chef for a simple local DNS solution. Basically, what I want is to be able to do this (or something similar):
nodes.each do |n|
dns_server “add-n-to-dns-server” do
name n[:server_name] + “.” + node.chef_environment # e.g. server001.testing
not_if # or have the dns provider handle this provision
Then point my local servers to use the server running this cookbook as their primary DNS for local resolution
I’ve been toying with djbdns all day, but it isn’t working as advertised. One, it isn’t centos ready, and the bluepill code isn’t finished for the server config. Is there a simple DNS cookbook that’s pre-baked that might work for me? I’m even willing to use bind if it “just works”.
Have a look at the latest versions of the djbdns and bluepill cookbooks on github github.com/opscode/cookbooks
There have been some recent commits to fix exactly this, and I’m not sure they have been released yet.
Once you get past the bluepill issue, depending on your usage pattern you may run into other problems.
We have been using djbdns for our HQ (private) DNS for months and it works; but we have local patches.
I have been looking at merging those backs, but I would love some external testing first. If you are willing to try, I can clean those up and send them to you. If they work for you I will take care of getting them merged.
Thanks in advance. And for all the developers who read this list, thank you for all you do. Chef is great!