Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


bind-ddns (16) Versions 1.4.0

Install and configure ISC Bind on server and nsupdate on clients

cookbook 'bind-ddns', '= 1.4.0', :supermarket
cookbook 'bind-ddns', '= 1.4.0'
knife supermarket install bind-ddns
knife supermarket download bind-ddns
Quality 100%



Install and configure ISC Bind with
full Dynamic DNS support.

On client side, install nsupdate, provide a generic provider and a recipe
to update DNS entries.


Cookbooks and gems

Declared in [metadata.rb](metadata.rb) and in [Gemfile](Gemfile).


  • RHEL Family 7, tested on Centos

Note: it should work fine on Debian 8 but the official docker image does not
allow systemd to work easily, so it could not be tested.


Easy Setup

Add recipe[bind-ddns::server] in your run-list to install and configure
Bind. Configuration will be fetched from attributes options, zones and

To add a client, add recipe[bind-ddns::client]. nsupdate recipe will
update all records defined in records.

To see an example, look at [.kitchen.yml](.kitchen.yml).


This cookbook is fully tested through the installation of a server and a client
in docker hosts. This uses kitchen, docker and some monkey-patching.

If you run kitchen list, you will see 2 suites, Each corresponds to a different

  • server-ddns-centos-7: Bind server
  • client-ddns-centos-7: DNS client with nsupdate

For more information, see [.kitchen.yml](.kitchen.yml) and [test](test)


Configuration is done by overriding default attributes. All configuration keys
have a default defined in [attributes/default.rb](attributes/default.rb).
Please read it to have a comprehensive view of what and how you can configure
this cookbook behavior.

Note: for fields needing an IP address, it is possible to set an interface
name, which will be resolved to its first non-local address.

Specific configuration (client or server)

To allow clients and servers to share a same role, it is possible to define
specific configuration keys applicable to one of the status (client or server).

Specific configurations can be any of the attributes defined in
[attributes/default.rb](attributes/default.rb) but in either "client-config"
or "server-config" sub-tree.

A node is declared as server if its FQDN is included in attribute
"['bind-ddns']['servers']" defined as an array. Else, it is considered
as a client.



Call init and then, following the node status, call client or
server recipe.


Determine if the current machine is a server or a client. Write the result
in "run_state['bind-ddns']['status']". Then merge default and specific
(client or server) configurations and store the result in

Note: init is included in all recipes.


Install Bind package.


Install Bind utils package.


Configure Bind server: named.conf, keys and zones.
Then check configuration through named-checkconf.


Enable and start named service, subscribes on named-checkconf resource.


Call bind-ddns default provider (which call nsupdate command) based on
attribute records. See [.kitchen.yml](.kitchen.yml) for more information.

Replace some missing configuration attributes:
- domain (name attribute) by the FQDN
- data by the ip defined in "node[:ipaddress]"
- zone by the tail part of the domain


Set resolv.conf using server attribute.


Install Bind utils, configure resolv.conf if requested (by attribute
set_resolv_conf) with recipe resolvconf and call nsupdate recipe.


Install, configure and launch Bind. Then call client recipe.



Add, update or remove a DNS record using nsupdate. Read the
[resources/default.rb](resource file) for more details.

Simple example:
bind_ddns '' do
server ''
data ""
keyname 'foo'
secret 'XXXX'

Use action :delete to delete an entry (default is :add).




Please read carefully []( before making a merge

License and Author

Copyright:: 2015-2016, Sam4Mobile

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Changelog ========= 1.4.0 ----- Main: - Can use specific options for clients or servers, to allow clients and servers to share the same role + Add an init recipe which initialize the configuration correctly + Modify default to choose between client and server recipe + client specific configurations should be in 'client-config' and servers in 'server-config' + the servers should be defined with 'servers' key + backward compatibility is not broken - Switch to docker_cli, use prepared docker image + Switch kitchen driver from docker to docker_cli + Use sbernard/centos-systemd-kitchen image instead of bare centos + Remove privileged mode :) + Remove some now useless monkey patching + Fix a typo in kitchen_command, fixing kitchen create command Misc: - Fix default options not merged with user attributes - Improve documentation, explain resource attributes and specific configurations - Better tests, to test specific option behavior - Fix all rubocop offenses + In particular, package-client recipe is renamed to package_client 1.3.1 ----- - Fix deprecated behavior (using nil as argument for a default resource) 1.3.0 ----- - Use lazy to simplify the definition of template "#{filepath}.erb" - Small cleanup of default provider & resource, key info are required - Fix idempotency by removing the block hack used to run the resource - Add a test case on :delete for default provider 1.2.0 ----- - Add option for secondary servers in resolv.conf - Reorganize README: + Move changelog from README to CHANGELOG + Move contribution guide to + Reorder README, fix Gemfile missing - Add Apache 2 license file 1.1.0 ----- - Fix failed run when a zone is reloaded while named is stopped - Fix failed run when an interface name is used for its ip and this ip is fetched during the same run - Fix failed run when a zone is modified while named is stopped - Remove useless field 'hmac' in resource and provider 1.0.1 ----- - Fix default hostmaster email 1.0.0 ----- - Initial version with Centos 7 support

Foodcritic Metric

1.4.0 passed this metric