](http://www.apache.org/licenses/LICENSE-2.0.html)

Table of Contents

1. Description
2. Setup - The basics of getting started with resolv
   • What resolv affects
   • Setup requirements
   • Beginning with resolv
3. Usage - Configuration options and additional functionality
4. Reference - An under-the-hood peek at what the module is doing and how
5. Limitations - OS compatibility, etc.
6. Development - Guide for contributing to the module
   • Acceptance Tests - Beaker env variables

Description

This module sets up DNS client config, including /etc/resolv.conf and /etc/host.conf.

This is a SIMP module

This module is a component of the System Integrity Management Platform, a compliance-management framework built on Puppet.

If you find any issues, they may be submitted to our bug tracker.

This module is optimally designed for use within a larger SIMP ecosystem, but it can be used independently:

• When included within the SIMP ecosystem, security compliance settings will be managed from the Puppet server.

Setup

What resolv affects

• /etc/resolv.conf
• /etc/host.conf
• Network Manager

Beginning with resolv

Include the class on any systems you want to manage.

Usage

Include the class from hiera:

---
classes:
  - ::resolv

File contents can be tweaked by adding more hieradata:

---
resolv::rotate: false
resolv::host_conf::multi: true

nmcli

Managing device DNS entries can be done via nmcli accordingly:

---
resolv::use_nmcli: true
resolv::nmcli_connection_name: 'System eth0'
resolv::nmcli_ignore_auto_dns: true
resolv::nmcli_auto_reapply_device: true

Reference

Please refer to the REFERENCE.md.

Limitations

SIMP Puppet modules are generally intended for use on Red Hat Enterprise Linux and compatible distributions, such as CentOS. Please see the metadata.json file for the most up-to-date list of supported operating systems, Puppet versions, and module dependencies.

Development

Please read our [Contribution Guide] (https://simp.readthedocs.io/en/stable/contributors_guide/index.html).