A Local Resolver That Validates What It Answers
Unbound on loopback: DNSSEC validated locally against the root anchor, query names minimised, version hidden, and upstream over DNS-over-TLS by default because many networks reset TCP 53 to anything but a known resolver, which breaks full recursion the moment a DNSKEY answer outgrows UDP. Recursion is one setting away. Original role, live-tested on Rocky Linux 10.
Verification
Live-testedReally deployed to a container sandbox, proven idempotent (a second run changes nothing), verified against the role’s assertions, then torn down.
Conformance
- Static validation (yamllint · ansible-lint)
Provenance
- SHA-256 checksum
- Signature (pending)
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-09-19 · podman 4.9.3 · ansible 2.21.4 · how we verify
Cite it in your README
badge · attributionPaste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads live-tested because the record says so, and the link lands on this page.
[](https://www.iac-bazaar.com/catalog/ansible-unbound-resolver?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
Ansible role 1.0.0, live-tested on IaC Bazaar: [A Local Resolver That Validates What It Answers](https://www.iac-bazaar.com/catalog/ansible-unbound-resolver?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)
```yaml
# A Local Resolver That Validates What It Answers: https://www.iac-bazaar.com/catalog/ansible-unbound-resolver (download from your IaC Bazaar account)
```Preview:
Documentation
unbound-resolver
A local Unbound resolver: DNSSEC-validating, caching, name-minimising, and answering on loopback only. Original role for EL 9 and 10, live-tested with podman on Rocky Linux 10.
The package ignores its own drop-in directories. EL's unbound.conf
ships conf.d/ and local.d/ beside it but no active include: of either -
only commented examples - so a file dropped into conf.d changes nothing. This
role writes the whole unbound.conf, validated by unbound-checkconf before it
is installed, and includes both directories from it so your additions work.
Answers are validated, not just cached. With auto-trust-anchor-file
pointing at the root key the package keeps current, a forged or stripped answer
is refused rather than served for a day. The verify step asks for example.com
with DNSSEC and asserts the ad flag came back.
It says as little as possible. Query-name minimisation sends each upstream
only the labels it needs, hide-identity and hide-version refuse
version.bind, and minimal-responses keeps additional data out.
Encrypted forwarding is the default; recursion is the switch. Queries go
to Quad9 over DNS-over-TLS, with the certificate checked against the system
bundle, and every answer is validated locally all the same. Set
unbound_resolver_forwarders: [] for full recursion from the root servers -
with one thing measured rather than assumed while building this role: on a
network that resets TCP 53 to anything but a known resolver (the one this was
tested from does), recursion fails outright, because the root DNSKEY answer is
larger than the 1232-byte EDNS buffer, is truncated, falls back to TCP, and
the TCP connection is reset. "No servers could be reached" is the whole
symptom. Over DNS-over-TLS the same answer arrives whole.
License
Commercial - IaC Bazaar EULA. (c) IaC Bazaar.
Usage code & full reference need an account
The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.
- Variables
- Test
Related modules
ansible-bind-authoritative
BIND as an authoritative-only server. The package is a loopback resolver; add a zone and anyone who can query can copy the whole zone, and version.bind names the 9.18 to attack. This role turns recursion off, refuses transfers to anyone not listed, hides the identity records, rate-limits responses, and renders zones from data checked before they land. Original role, live-tested on Rocky Linux 10.
ansible-coredns
CoreDNS from the upstream release (sha256-verified) as a hardened system service answering authoritatively for your zones on 127.0.0.1:53 as a system user (CAP_NET_BIND_SERVICE through the unit), forwarding only when you name upstreams. The live test digs the example zone's A record with the aa flag, an NXDOMAIN in the zone and a REFUSED outside it. Original role, live-tested on Rocky Linux 10.
ansible-knot
Knot DNS from EPEL as an authoritative server that signs your zones with DNSSEC, keeps your zone files as written and serves a change with no serial to bump. As installed the package cannot start. The live test validates answers with delv against the zone's own key, and is refused a transfer without the TSIG key. Original role, live-tested on Rocky Linux 10.
ansible-nsd
NSD from EPEL: an authoritative-only server for your zones, the configuration and every zone checked by NSD's own tools first, transfers only to the addresses and TSIG keys you name, response rate limiting, and the state directory the package leaves unwritable fixed. The live test gets the zone with the key and is refused without it. Original role, live-tested on Rocky Linux 10.
ansible-pdns-recursor
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.
ansible-powerdns
PowerDNS authoritative from EPEL with its SQLite backend; the live test adds a zone through the API, gets the record from dig and NXDOMAIN for an unknown name, sees the API refuse a caller with no key, and reads the query counter. The schema is recovered when a docs-stripped host lacks it. Original role, live-tested on Rocky Linux 10.