Forge Home


The unbound module manages unbound


9,995 latest version

3.2 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.0 (latest)
released Dec 16th 2012

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'oppegaard-unbound', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add oppegaard-unbound
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install oppegaard-unbound --version 0.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



oppegaard/unbound — version 0.1.0 Dec 16th 2012

== Class: unbound

The unbound class manages unbound, the reqursive caching DNS resolver. It manages the package, service, configuration file, control keys and support files.

Supported operating systems are OpenBSD. Tested on OpenBSD 5.2 with Puppet 2.7.14.

The configuration file is concatenated from samples of server et. al., stub-zone and forward-zone. The latter two are created independently from the server settings, by defines which can be used by other classes and modules.

Control keys can be created with the unbound-control-setup program, and is enabled by default. These are neccessary to be able to control unbound (restart, reload etc) with the unbound-control program.

The auto-trust-anchor-file 'root.key' can be created with the unbound-anchor program, and is enabled by default.

The root-hints files named.cache can be managed, but have to be provided by the user. See the documentation in manifests/root_hints.pp for how to proceede. This functionality is not enabled by default.

=== Parameters

[settings] Hash containing the settings as key value pairs.

[ssl] Mange unbound-control certificates? True or false, true by default.

[anchor] Manage root.key? True or false, true by default.

[root_hints] Manage named.cache? True or false, false by default.

=== Examples

class { 'unbound': root_hints => true, settings => { server => { verbosity => '1', interface => [ '', '::1', $::ipaddress, ], outgoing-interface => $::ipaddress, access-control => [ ' allow', '::1 allow', ' allow', ], root-hints => '"/var/unbound/etc/named.cache"', private-address => [ '', '', '', ], private-domain => "\"$::domain\"", auto-trust-anchor-file => '"/var/unbound/etc/root.key"', }, python => { }, remote-control => { control-enable => 'yes', control-interface => [ '', '::1', ], }, } }

See manifests/stub.pp and manifests/forward.pp for examples on how to create sub zones and forward zones repectively.