Forge Home

pdns

PowerDNS nameserver or resolver

13,142 downloads

11,119 latest version

2.6 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.4.0 (latest)
  • 0.3.2
  • 0.3.1
  • 0.3.0
  • 0.2.0
  • 0.1.0
  • 0.0.2
  • 0.0.1
released Nov 8th 2012

Start using this module

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

Add this module to your Puppetfile:

mod 'erwbgy-pdns', '0.4.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add erwbgy-pdns
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install erwbgy-pdns --version 0.4.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.

Download

Documentation

erwbgy/pdns — version 0.4.0 Nov 8th 2012

puppet-pdns

Manage PowerDNS configuration using Puppet

Run either a PowerDNS name server or a PowerDNS resolver, making it easy to use an internal domain.

In puppet node config we include the class:

include pdns

Configure the name server and/or resolver using hiera configuration - for example:

pdns:
  nameserver:
    backend:        'sqlite'
    listen_address: '192.168.0.3'
    forward_domain: 'local'
  resolver:
    listen_address: '127.0.0.1'
    forward_domain: 'local'
    nameservers:    '192.168.0.3,192.168.0.4'

pdns::nameserver

Run a PowerDNS name server to authoritatively answer hostname/IP queries from DNS resolvers for a specific set of domains managed by the name server.

Parameters

use_hiera: look up configuration under 'pdnsnameserver' hash in hiera. Default: _true

backend: database backend to use - one of: sqlite or postgresql. Default: sqlite.

listen_address: IP to listen on. Default: $::ipaddress

forward_domain: Internal domain name (eg. .local). Default: undef

reverse_domain: Reverse .in-addr.arpa domain name for the forward domain (eg. 10.in-addr.arpa). If forward domain is specified and this is not set then it is derived from the listen_address. Default: undef

Hiera configuration

Parameters can be specified in hiera configuration files under the 'pdns nameserver' hash:

Example:

pdns:
  nameserver:
    backend:        'sqlite'
    listen_address: '192.168.0.3'
    forward_domain: 'local'

Examples

In puppet node config we just include the class:

include pdns::nameserver

Assuming that the primary IP address is a 10.17.0.1:

1) PowerDNS name server with SQLite backend

No hiera config or hiera config:

pdns:
  nameserver:
    backend:        'sqlite'

which is the same as:

pdns:
  nameserver:
    backend:        'sqlite'
    listen_address: '10.17.0.1'

2) PowerDNS name server with Postgresql backend:

Hiera config:

pdns:
  nameserver:
    backend:        'postgresql'

which is the same as:

pdns:
  nameserver:
    backend:        'postgresql'
    listen_address: '10.17.0.1'

3) PowerDNS name server configured with an internal .local domain:

Hiera config:

pdns:
  nameserver:
    forward_domain: 'local'

which is the same as:

pdns:
  nameserver:
    backend:        'sqlite',
    listen_address: '10.17.0.1',
    forward_domain: 'local',
    reverse_domain: '10.in-addr.arpa',

Scripts

Use the add_host script to add an A record for a hostname - for example add an A record for the prod1 host with IP 10.0.0.3:

# /etc/pdns/add_host prod1 10.0.0.3
Adding A record for host x120.local with IP 10.0.0.3: ok
Adding PTR record for IP 10.0.0.3 with host prod1.local: ok
Restarting name server: ok
$ host prod1
prod1.local has address 10.0.0.3

Use the add_cname script to add an CNAME record (alias) for a hostname - for example to add an alias for the prod1 host called puppet:

# /etc/pdns/add_cname puppet prod1
Adding CNAME record: alias puppet.local, host prod1.local: ok
Restarting name server: ok
$ host puppet
puppet.local is an alias for prod1.local.
prod1.local has address 10.0.0.1

Use the show script to see the entries in the database - for example:

# /etc/pdns/show 
           name            | type  |   content    
---------------------------+-------+--------------
 server1.local             | A     | 10.47.73.125
 ns1.local                 | CNAME | server1.local
 prod2.local               | A     | 10.0.0.4
 alias2.local              | CNAME | prod2.local
 10.in-addr.arpa           | NS    | ns1.local
 local                     | NS    | ns1.local
 125.73.47.10.in-addr.arpa | PTR   | ns1.local
 4.0.0.10.in-addr.arpa     | PTR   | prod2.local
 10.in-addr.arpa           | SOA   | ns1.local
 local                     | SOA   | ns1.local
(10 rows)

pdns::resolver

Run a PowerDNS resolver that contacts the appropriate DNS name servers on behalf of clients to covert a hostname into an IP or an IP into a hostname. (The IP address of a DNS resolver is what is specified in /etc/resolv.conf on Linux/Unix hosts.)

Parameters

use_hiera: look up configuration under the 'pdns resolver' hash in hiera. Default: true

listen_address: IP to listen on. Default: $::ipaddress

dont_query: IP ranges to exclude from lookups. Default: '127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12, ::1/128'

forward_zones: Array of = values specifying where to send queries for specific domain. Default: undef

forward_domain: Internal domain name (eg. .local). Default: undef

reverse_domain: Reverse .in-addr.arpa domain name for the forward domain (eg. 10.in-addr.arpa). If forward domain is specified and this is not set then it is derived from the listen_address. Default: undef

nameservers: Comma-separated list of the IP addresses of the authoritative nameservers for the internal domain name specified in $forward_domain. Default: $::ipaddress

Hiera configuration

Parameters can be specified in hiera configuration files under the 'pdns_resolver' hash:

Example:

pdns:
  resolver:
    listen_address: '127.0.0.1'
    forward_domain: 'local'
    nameservers:    '192.168.0.3,192.168.0.4'

Examples

In puppet node config we just include the class:

include pdns::resolver

Assuming that the local IP address is 192.168.0.72 and there is a authoritative name server for an internal .local domain at 192.168.0.2:

1) Basic PowerDNS resolver:

No hiera config which is the same as:

pdns:
  resolver:
    listen_address: 192.168.0.72

3) PowerDNS resolver configured to send queries for a .local domain to the specified name server:

Hiera config:

pdns:
  resolver:
    forward_domain: 'local',
    nameservers:    '192.168.0.2'

which is the same as:

pdns:
  resolver:
    listen_address: '192.168.0.72'
    dont_query:     '127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, ::1/128'
    forward_domain: 'local'
    reverse_domain: '168.192.in-addr.arpa'
    nameservers:    '192.168.0.2'

or:

pdns:
  resolver:
    listen_address: '192.168.0.72'
    dont_query:     '127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, ::1/128'
    forward_zones:
      - 'local=192.168.0.2'
      - '168.192.in-addr.arpa=192.168.0.2'

4) PowerDNS resolver configured to send queries for a .local domain to the specified name server and network (192.168.0.0/24) for reverse lookups:

Hiera config:

pdns:
  resolver:
    forward_domain: 'local'
    forward_zones:
      - 'local=192.168.0.2'
      - '0.168.192.in-addr.arpa=192.168.0.2'

which is the same as:

pdns:
  resolver:
    listen_address: '192.168.0.72'
    dont_query:     '127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, ::1/128'
    forward_zones:
      - 'local=192.168.0.2'
      - '0.168.192.in-addr.arpa=192.168.0.2'

or:

pdns:
  resolver:
    listen_address: '192.168.0.72'
    dont_query:     '127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, ::1/128'
    forward_domain: 'local'
    reverse_domain: '0.168.192.in-addr.arpa'
    nameservers:    '192.168.0.2'

Testing

Tests are implemented using RSpec, rspec-puppet and puppetlabs_spec_helper. To run them you will first need to install puppetlabs_spec_helper:

# gem install puppetlabs_spec_helper

Then switch to the module directory and run rake:

$ rake
rake build            # Build puppet module package
rake clean            # Clean a built module package
rake coverage         # Generate code coverage information
rake help             # Display the list of available rake tasks
rake lint             # Check puppet manifests with puppet-lint
rake spec             # Run spec tests in a clean fixtures directory
rake spec_clean       # Clean up the fixtures directory
rake spec_prep        # Create the fixtures directory
rake spec_standalone  # Run spec tests on an existing fixtures directory

$ rake spec
/usr/bin/ruby -S rspec spec/classes/pdns__resolver_spec.rb spec/classes/pdns__nameserver_spec.rb spec/classes/pdns__resolver__config_spec.rb spec/classes/pdns__nameserver__config_spec.rb --color
...............

Finished in 5.19 seconds
15 examples, 0 failures

Support

License: Apache License, Version 2.0

GitHub URL: https://github.com/erwbgy/puppet-pdns