cookbook 'bind-ddns', '= 1.0.1'
bind-ddns (16) Versions 1.0.1 Follow2
Install and configure ISC Bind on server and nsupdate on clients
cookbook 'bind-ddns', '= 1.0.1', :supermarket
knife supermarket install bind-ddns
knife supermarket download bind-ddns
Install and configure ISC Bind https://www.isc.org/downloads/bind/ with
full Dynamic DNS support.
On client side, install nsupdate, provide a generic provider and a recipe
to update DNS entries.
recipe[bind-ddns::server] in your run-list to install and configure
Bind. Configuration will be fetched from attributes
To add a client, add
recipe[bind-ddns::client]. nsupdate recipe will
update all records defined in
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)
- Initial version with Centos 7 support
Declared in [metadata.rb](metadata.rb).
Declared 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.
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.
Call recipe client.
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
records. See [.kitchen.yml](.kitchen.yml) for more information.
Set resolv.conf using
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 or remove a DNS record using nsupdate:
bind_ddns 'test.foo' do
:delete to delete an entry.
You are more than welcome to submit issues and merge requests to this project.
Your commits must pass
git log --check and messages should be formated
like this (based on this excellent
Summarize change in 50 characters or less Provide more detail after the first line. Leave one blank line below the summary and wrap all lines at 72 characters or less. If the change fixes an issue, leave another blank line after the final paragraph and indicate which issue is fixed in the specific format below. Fix #42
Also do your best to factor commits appropriately, ie not too large with
unrelated things in the same commit, and not too small with the same small
change applied N times in N different commits. If there was some accidental
reformatting or whitespace changes during the course of your commits, please
rebase them away before submitting the MR.
All files must be 80 columns width formatted (actually 79), exception when it
is not possible.
License and Author
- Author:: Samuel Bernard (email@example.com)
Copyright:: 2015, 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 http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
This cookbook has no specified dependencies.
There are no cookbooks that are contingent upon this one.
1.0.1 passed this metric
1.0.1 passed this metric