Forge Home

unbound

Puppet Module for managing Unbound

8,688 downloads

4,282 latest version

5.0 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

  • 2.0.1 (latest)
  • 2.0.0
  • 1.0.0
released May 19th 2019
This version is compatible with:
  • Puppet Enterprise 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=4.6.0 <6.0.0
  • , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'bodgit-unbound', '2.0.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install bodgit-unbound --version 2.0.1

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.

Download
Tags: dns, unbound

Documentation

bodgit/unbound — version 2.0.1 May 19th 2019

unbound

Tested with Travis CI

Build Status Coverage Status Puppet Forge Dependency Status

Table of Contents

  1. Description
  2. Setup - The basics of getting started with unbound
  3. Usage - Configuration options and additional functionality
  4. Reference - An under-the-hood peek at what the module is doing and how
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module

Description

This module manages Unbound.

RHEL/CentOS and OpenBSD are supported using Puppet 4.6.0 or later.

Setup

Beginning with unbound

In the simplest case, configure Unbound listening on all interfaces:

include ::unbound

Usage

Update the above example to specify the forwarders to use and allow access from the local network, also restrict outbound ports used to avoid anything below 32768 and above 65000:

class { '::unbound':
  access_control => [
    ["${::network}/${netmask_to_masklen($::netmask)}", 'allow'],
    ["${::network6}/${netmask_to_masklen($::netmask6)}", 'allow'],
  ],
  outgoing_port  => [
    ['avoid', 0, 32767],
    ['avoid', 65001, 65535],
  ],
}

::unbound::forward { '.':
  forward_addr => [
    '8.8.8.8',
    '8.8.4.4',
    '2001:4860:4860::8844',
    '2001:4860:4860::8888',
  ],
}

Configure NSD listening on the primary interface as a slave for a single zone protected with a given TSIG key and configure Unbound listening on the loopback interface only with a stub zone pointing to NSD:

class { '::nsd':
  ip_address => [
    $::ipaddress,
    $::ipaddress6,
  ],
}

::nsd::key { 'example.':
  algorithm => 'hmac-sha256',
  secret    => '6z+8iKRIQrwN43TFfO/Rf2NHzpHIFVi6PsJ7dDESclc=',
}

::nsd::zone { 'example.com.':
  allow_notify => [
    ['192.0.2.1', 'example.'],
  ],
  request_xfr  => [
    ['AXFR', '192.0.2.1', 'example.'],
  ],
}

class { '::unbound':
  interface => [
    $::ipaddress_lo,
    $::ipaddress6_lo,
  ],
}

::unbound::stub { 'example.com.':
  stub_addr => [
    $::ipaddress,
    $::ipaddress6,
  ],
}

If NSD is not required then local data can be used instead:

class { '::unbound':
  interface  => [
    $::ipaddress_lo,
    $::ipaddress6_lo,
  ],
  local_zone => [
    ['example.com.', 'static'],
  ],
  local_data => [
    {
      'name'     => 'example.com.'
      'ttl'      => 86400,
      'class'    => 'IN',
      'type'     => 'NS',
      'hostname' => 'ns1.example.com.',
    },
    {
      'name'     => 'example.com.'
      'ttl'      => 86400,
      'class'    => 'IN',
      'type'     => 'SOA',
      'primary'  => 'ns1.example.com.',
      'email'    => 'hostmaster.example.com.',
      'serial'   => 1,
      'refresh'  => 10800,
      'retry'    => 15,
      'expire'   => 604800,
      'negative' => 10800,
    },
    {
      'name'  => 'ns1.example.com.',
      'ttl'   => 86400,
      'class' => 'IN',
      'type'  => 'A',
      'ip'    => '192.0.2.1',
    },
  ],
}

Reference

The reference documentation is generated with puppet-strings and the latest version of the documentation is hosted at https://bodgit.github.io/puppet-unbound/.

Limitations

This module has been built on and tested against Puppet 4.6.0 and higher.

The module has been tested on:

  • RedHat Enterprise Linux 6/7
  • OpenBSD 6.0/6.1

Development

The module has both rspec-puppet and beaker-rspec tests. Run them with:

$ bundle exec rake test
$ PUPPET_INSTALL_TYPE=agent PUPPET_INSTALL_VERSION=x.y.z bundle exec rake beaker:<nodeset>

Please log issues or pull requests at github.