unbound
This module sets up a recursive DNS service with root hints using the unbound package.
Version information
released Jul 30th 2019
This version is compatible with:
- Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2016.4.x
- Puppet >= 4.10.0 < 7.0.0
- , , , , ,
Start using this module
Add this module to your Puppetfile:
mod 'tsaterdal-unbound', '0.2.2'
Learn more about managing modules with a PuppetfileDocumentation
tsaterdal/unbound — version 0.2.2 Jul 30th 2019
unbound
This module manages unbound DNS.
Table of Contents
- Description
- Setup - The basics of getting started with unbound
- Usage - Configuration options and additional functionality
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Description
This module provides a recursive DNS server using the unbound service. It can be used a a simple outbound resolver in the infrastructure, and also with custom private subdomains. See Usage for examples.
Setup
What unbound affects
Beginning with unbound
The very basic steps needed for a user to get the module up and running. This can include setup steps, if necessary, or it can be an example of the most basic use of the module.
Usage
If you want to host a custom subdomain on a authorative dns server, additional configuration is supplied such:
class profile::unbound {
include unbound
unbound::config { 'example.com':
content => template('profile/unbound/example.com.epp'),
}
}
The additional config is set up as:
example.com.epp, under templates in your control repo
server:
verbosity: 3
log-queries: yes
log-replies: yes
#Add local zones here
access-control: 10.0.0.0/24 allow
access-control: ::ffff:a00:0/64 allow
private-domain: "example.com"
insecure-lan-zones: yes
local-zone: "10.in-addr.arpa." nodefault
forward-zone:
name: "10.in-addr.arpa"
forward-addr: 10.0.0.254
Limitations
Development
This module is under development, and further features will be added