authoritative servers #3607

New issue

Closed

opened 2026-03-16 11:52:53 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 11:52:53 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/3166
Author: @cpu
Created: 7/29/2025
Status: ✅ Merged
Merged: 8/5/2025
Merged by: @cpu

Base: main ← Head: cpu-pdns-conformance

📝 Commits (3)

d6d6f07 dns-test: have explore say which image its building
b5ffe90 dns-test: support pdns recursor/forwarder
3f23b97 dns-test: support pdns authoritative server

📊 Changes

14 files changed (+289 additions, -3 deletions)

View changed files

📝 conformance/README.md (+2 -0)
➕ conformance/chain.pem (+36 -0)
➕ conformance/key.pem (+5 -0)
📝 conformance/packages/dns-test/examples/explore.rs (+5 -3)
📝 conformance/packages/dns-test/src/container.rs (+10 -0)
➕ conformance/packages/dns-test/src/docker/pdns.Dockerfile (+30 -0)
📝 conformance/packages/dns-test/src/implementation.rs (+39 -0)
📝 conformance/packages/dns-test/src/lib.rs (+4 -0)
📝 conformance/packages/dns-test/src/name_server.rs (+22 -0)
📝 conformance/packages/dns-test/src/resolver.rs (+17 -0)
➕ conformance/packages/dns-test/src/templates/pdns-auth.conf.jinja (+25 -0)
➕ conformance/packages/dns-test/src/templates/pdns-zones.conf.jinja (+15 -0)
➕ conformance/packages/dns-test/src/templates/pdns.forwarder.conf.jinja (+38 -0)
➕ conformance/packages/dns-test/src/templates/pdns.resolver.conf.jinja (+41 -0)

📄 Description

This branch extends the existing dns-test framework to allow testing with powerdns acting as a recursive resolver, a forwarding resolver, or an authoritative server. PowerDNS seems to have one of the more complete RFC 9539 implementations, and so having it integrated into the dns-test framework is helpful while looking at equivalent support in our resolver/auth server.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/hickory-dns/hickory-dns/pull/3166 **Author:** [@cpu](https://github.com/cpu) **Created:** 7/29/2025 **Status:** ✅ Merged **Merged:** 8/5/2025 **Merged by:** [@cpu](https://github.com/cpu) **Base:** `main` ← **Head:** `cpu-pdns-conformance` --- ### 📝 Commits (3) - [`d6d6f07`](https://github.com/hickory-dns/hickory-dns/commit/d6d6f07e988c10eb5378f325fcf20f74302c99ff) dns-test: have explore say which image its building - [`b5ffe90`](https://github.com/hickory-dns/hickory-dns/commit/b5ffe907f1ea46127df52d63369dfa5397359cae) dns-test: support pdns recursor/forwarder - [`3f23b97`](https://github.com/hickory-dns/hickory-dns/commit/3f23b975ab96fd4e229cfd1ddc8f5a448e68efd1) dns-test: support pdns authoritative server ### 📊 Changes **14 files changed** (+289 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `conformance/README.md` (+2 -0) ➕ `conformance/chain.pem` (+36 -0) ➕ `conformance/key.pem` (+5 -0) 📝 `conformance/packages/dns-test/examples/explore.rs` (+5 -3) 📝 `conformance/packages/dns-test/src/container.rs` (+10 -0) ➕ `conformance/packages/dns-test/src/docker/pdns.Dockerfile` (+30 -0) 📝 `conformance/packages/dns-test/src/implementation.rs` (+39 -0) 📝 `conformance/packages/dns-test/src/lib.rs` (+4 -0) 📝 `conformance/packages/dns-test/src/name_server.rs` (+22 -0) 📝 `conformance/packages/dns-test/src/resolver.rs` (+17 -0) ➕ `conformance/packages/dns-test/src/templates/pdns-auth.conf.jinja` (+25 -0) ➕ `conformance/packages/dns-test/src/templates/pdns-zones.conf.jinja` (+15 -0) ➕ `conformance/packages/dns-test/src/templates/pdns.forwarder.conf.jinja` (+38 -0) ➕ `conformance/packages/dns-test/src/templates/pdns.resolver.conf.jinja` (+41 -0) </details> ### 📄 Description This branch extends the existing `dns-test` framework to allow testing with [powerdns](https://www.powerdns.com/) acting as a recursive resolver, a forwarding resolver, or an authoritative server. PowerDNS seems to have one of the more complete RFC 9539 implementations, and so having it integrated into the `dns-test` framework is helpful while looking at equivalent support in our resolver/auth server. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>