Forge Home


Module to manage Windows DNS server instances


1,690 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

  • 0.1.0 (latest)
released Mar 31st 2021
This version is compatible with:
  • Puppet Enterprise 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, 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
  • Puppet >= 5.5.18 < 8.0.0

Start using this module

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

Add this module to your Puppetfile:

mod 'arden-win_dns_server', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add arden-win_dns_server
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install arden-win_dns_server --version 0.1.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.

Tags: facts


arden/win_dns_server — version 0.1.0 Mar 31st 2021


pipeline status Version coverage report

Table of Contents

  1. Description
  2. Setup - The basics of getting started with win_dns_server
  3. Usage
  4. Limitations
  5. Development - Guide for contributing to the module


This module provides a basic method to manage the configuration of the DNS server feature on a Windows server instance. While much of the configuration is accomplished via PowerShell DSC it was necessary to implement a new wrapper for the currently unsupported Conditional Forwarder Zone types.


Setup Requirements

Pluginsync should be enabled. Additionally, you'll need to perform the configuration steps detailed for the DSC, pwshlib, and the resource_api module.

Beginning with win_dns_server

The following example will configure the DNS service, perform some basic global settings, and create two forwarder zones.

  debug_log_path: 'C:\temp\dns_debug.log'
  disable_recursion: false
  round_robin_responses: true
  - ''
  - ''
      - ''
      - ''
    use_recursion: false


Currently AD backed DNS servers are only supported in a limited form. You should not try to create conditional forwarder zones on them!

Also, if the target zone already exists but is of the incorrect type things will go sideways. This is poorly tested at the moment, however, I believe the command will silently fail to create the target zone.


Make a pull request and we'll figure it out!