PowerDNS Recursor Over TLS To Forwarders It Checks By Name

PowerDNS Recursor from EPEL on loopback: DNSSEC validated, and every upstream query sent over DNS-over-TLS with each forwarder's certificate checked against the name it must carry. The live test counts every upstream query as TLS, gets SERVFAIL for a broken signature, and has a copy naming the wrong certificate answer nothing. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticDNSv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Local Resolver That Validates What It Answers BIND That Answers For Its Zones And Nothing Else CoreDNS Authoritative On Loopback:53, Proven By dig NSD Authoritative DNS With Keyed Zone Transfers PowerDNS, A Zone It Answers For, From SQLite bind_exporter, A Query Counted Through BIND's Statistics Channel dnsdist With An ACL, A Rate Limit And A Cache

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_pdns_recursor" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-pdns-recursor/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.