Forge Home

Modules

Resources

PuppetEcosystemPuppet CommunityUpdates

bind

DNS bind/named config management.
Project URLRSS FeedReport issues

8,956 downloads

8,358 latest version

3.1 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.1 (latest)
  • 0.1.0
released Sep 2nd 2015
This version is compatible with:

Start using this module

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

Add this module to your Puppetfile:

mod 'covermymeds-bind', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add covermymeds-bind
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install covermymeds-bind --version 0.1.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: bind, dns, named

Documentation

covermymeds/bind — version 0.1.1 Sep 2nd 2015

Bind

Overview

This module installs and manages the bind package. The module is designed to get all of it's configuration variables from hiera. The zone data is pulled from an external source that returns JSON arrays and hiera. The external source needs to be a REST like service that takes the arguments appname, apptoken, and domain. An example of a data source is phpIPAM-api.

NOTE

Support for reverse lookup zones on subnets larger than CIDR /24 requires ruby gem netaddr.

bind:

Installs the named service, the module currently defaults to using a chroot environemnt. Defined types are called from this manifest to write the configuration file and zone data files.

bind::services

Controls the main named service and handles restarts when zone files change.

bind::zone_add

This defined type will get data from hiera to build the named.conf file and call the necessary defined type to build zone files. Zones are added to a name server by defining them in the host yaml file as shown below.

bind::domains:
  winbox.local:
    type: slave
       master:
         - 192.168.88.3
       slave:
         - 192.168.88.5
  example.com:
    type: master
      slave:
         - 192.168.88.5

To add domain records, add the data to hiera under the domain it belongs to. The same form applies for adding CNAME records to agiven domain, as shown below. MX and other record types will follow in the future.

....
bind::zones:
  example.com:
    ttl: 3600
    nameservers:
      - ns1.example.com
      - ns2.example.com
    data:
      foo: 192.168.135.5
      sally: 192.168.135.6
      dingbat: small-bird.local.

bind::fwd_zone

This defined type creates any forward lookup zones for bind, the data for the zone files will be a combination of hiera data and external data from some source. This defined type will also write the serial number for the zone file and call named-compilezone to insure there are server stopping errors.

bind::ptr_zone

This defined type will create a reverse lookup zone using the external data source. If you happen to have zones that are not CIDR 24, this defined type calls another defined type to handle those zones. For the time being only CIDR subnets larger than 24 are supported.