Forge Home

Modules

Puppet

Resources

PuppetEcosystemPuppet CommunityUpdates

named

manages either a chrooted named process or a caching nameserver
Project URLRSS FeedReport issues

14,013 downloads

77 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

  • 6.10.0 (latest)
  • 6.9.0
  • 6.8.0
  • 6.7.0
  • 6.6.0
  • 6.5.0
  • 6.4.0
  • 6.3.1
  • 6.3.0
  • 6.2.1
  • 6.2.0
  • 6.1.2
  • 6.1.1
  • 6.1.0
  • 6.0.3
  • 6.0.2
  • 6.0.1
  • 4.3.2
  • 4.3.1
released Sep 16th 2024
This version is compatible with:
  • Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x
  • Puppet >= 7.0.0 < 9.0.0
  • , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'simp-named', '6.10.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add simp-named
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install simp-named --version 6.10.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
Tags: bind, dns, named, simp

Documentation

simp/named — version 6.10.0 Sep 16th 2024

License CII Best Practices Puppet Forge Puppet Forge Downloads Build Status

named (BIND)

Table of Contents

  1. Module Description - What the module does and why it is useful
  2. Setup - The basics of getting started with named
  3. Usage - Configuration options and additional functionality
  4. Reference
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Acceptance Tests

Module Description

Installs, Configures and Manages a named service.

Options are available for caching and non-caching servers, and the choice between placing named in chroot or non_chroot with selinux enabled.

Caching

simp/named allows both the building of a non-caching named server via the named class or a caching server utilizing the named::caching class.

Chroot

This module will place named in a chroot at /var/named/chroot by default, but can be overrided and selinux enforced by adding a selinux_enforced variable to true in hiera or at the global variable level in the Puppet Console.

Setup

Install simp/named to your modulepath. A SIMP rsync server must also be in place to use the named module.

What named affects

simp/named manages the bind packages, named services, named user/group, named.conf, and the named directory and contents.

Begging with named

To setup the basic named server in chroot:

  class {'named':
    rsync_server => 'my.rsync.server',
  }

Usage

I want to use an selinux based named server not in chroot

Add the following to your Hiera File:

---
selinux_enforced: true

OR

Add selinux_enforced = true to the PE Console at the node or global level.

I want to make a caching named server

  class {'named::caching':
    rsync_server => 'my.rsync.server',
  }

Reference

See REFERENCE.md for the full module reference.

Limitations

SIMP Puppet modules are generally intended to be used on a Red Hat Enterprise Linux-compatible distribution.

Development

Please read our Contribution Guide.

If you find any issues, they can be submitted to our JIRA.

Acceptance tests

To run the system tests, you need Vagrant installed.

You can then run the following to execute the acceptance tests:

   bundle exec rake beaker:suites

Some environment variables may be useful:

   BEAKER_debug=true
   BEAKER_provision=no
   BEAKER_destroy=no
   BEAKER_use_fixtures_dir_for_modules=yes
  • BEAKER_debug: show the commands being run on the STU and their output.
  • BEAKER_destroy=no: prevent the machine destruction after the tests finish so you can inspect the state.
  • BEAKER_provision=no: prevent the machine from being recreated. This can save a lot of time while you're writing the tests.
  • BEAKER_use_fixtures_dir_for_modules=yes: cause all module dependencies to be loaded from the spec/fixtures/modules directory, based on the contents of .fixtures.yml. The contents of this directory are usually populated by bundle exec rake spec_prep. This can be used to run acceptance tests to run on isolated networks.