1. Module Description - What the module does and why it is useful
2. Setup - The basics of getting started with named
   • What named affects
   • Setup requirements
   • Beginning 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

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.

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.

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.

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

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

To setup the basic named server in chroot:

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

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.

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

• named: Main class for named.
• named::chroot: This class configures named in a chroot jail for execution on a system.
• named::install: Installs appropriate backages for BIND.
• named::non_chroot: This class configures named for execution on a system using seliunx.
• named::service: Manages named service.
• named::caching: Configures a caching name server
• named::hints: Determines what to add to named hints file.

• named::params: Parameters for named.

• named::caching::forwarders: Adds forwarders entries to your caching nameserver.

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

Please read our Contribution Guide.

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

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.