resolvconf

contributions requested
/etc/resolv.conf module

86,830 downloads

86,049 latest version

4.1 quality score

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.0.3 (latest)
  • 0.0.2
  • 0.0.1
released Jul 17th 2013

Start using this module

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

Add this module to your Puppetfile:

mod 'thias-resolvconf', '0.0.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add thias-resolvconf
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install thias-resolvconf --version 0.0.3

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

thias/resolvconf — version 0.0.3 Jul 17th 2013

puppet-resolvconf

Overview

Manage /etc/resolv.conf with puppet.

  • resolvconf : Main class.

The idea is to be able to globally include the resolvconf class on all nodes. From there, hiera with puppet 3.x allows to start managing the /etc/resolv.conf file's content in a very flexible way.

Examples

In site.pp :

hiera_include('classes')

In hieradata somewhere :

---
classes:
  - '::resolvconf'
resolvconf::header: ''
resolvconf::nameserver:
  - '198.51.100.1'
  - '198.51.100.2'
resolvconf::search:
  - 'foo.example.com'
  - 'bar.example.com'
  - 'example.com'

This way, only nodes where the Hiera values apply get their /etc/resolv.conf file modified by Puppet.