[PR #3188] [MERGED] e2e-tests: add pdns-recursor -> Hickory RFC 9539 test #3627

New issue

Closed

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

kerem commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/hickory-dns/hickory-dns/pull/3188
Author: @cpu
Created: 8/11/2025
Status: ✅ Merged
Merged: 8/19/2025
Merged by: @cpu

Base: main ← Head: cpu-dot-probe-test_dev

📝 Commits (1)

b462a9d e2e-tests: add pdns-recursor -> Hickory RFC 9539 test

📊 Changes

6 files changed (+187 additions, -0 deletions)

View changed files

📝 tests/e2e-tests/Cargo.lock (+1 -0)
📝 tests/e2e-tests/Cargo.toml (+1 -0)
📝 tests/e2e-tests/src/lib.rs (+1 -0)
➕ tests/e2e-tests/src/server.rs (+1 -0)
➕ tests/e2e-tests/src/server/dot.rs (+1 -0)
➕ tests/e2e-tests/src/server/dot/scenarios.rs (+182 -0)

📄 Description

Test the pdns recursive resolver RFC 9539 opportunistic DoT support works with Hickory. This is the last piece of groundwork/auth server work, and I'll be moving towards implementing equivalent probing support in hickory-resolver in subsequent follow-up PRs.

This tests the scenario where a client recursively queries through a pdns-recursor set up with DoT probing. After the recursor successfully discovers the HickoryDNS auth servers support DoT it should start upgrading its requests to use DoT instead of Do53 when querying those servers.

We can observe this by making recursive queries and interrogating the traffic that arrives at the 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/3188 **Author:** [@cpu](https://github.com/cpu) **Created:** 8/11/2025 **Status:** ✅ Merged **Merged:** 8/19/2025 **Merged by:** [@cpu](https://github.com/cpu) **Base:** `main` ← **Head:** `cpu-dot-probe-test_dev` --- ### 📝 Commits (1) - [`b462a9d`](https://github.com/hickory-dns/hickory-dns/commit/b462a9d7d4bfbc291f93867296faf9fb33402160) e2e-tests: add pdns-recursor -> Hickory RFC 9539 test ### 📊 Changes **6 files changed** (+187 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `tests/e2e-tests/Cargo.lock` (+1 -0) 📝 `tests/e2e-tests/Cargo.toml` (+1 -0) 📝 `tests/e2e-tests/src/lib.rs` (+1 -0) ➕ `tests/e2e-tests/src/server.rs` (+1 -0) ➕ `tests/e2e-tests/src/server/dot.rs` (+1 -0) ➕ `tests/e2e-tests/src/server/dot/scenarios.rs` (+182 -0) </details> ### 📄 Description Test the pdns recursive resolver [RFC 9539](https://www.rfc-editor.org/rfc/rfc9539.html) opportunistic DoT support works with Hickory. This is the last piece of groundwork/auth server work, and I'll be moving towards implementing equivalent probing support in hickory-resolver in subsequent follow-up PRs. This tests the scenario where a client recursively queries through a `pdns-recursor` set up with [DoT probing](https://blog.powerdns.com/2022/06/13/probing-dot-support-of-authoritative-servers-just-try-it). After the recursor successfully discovers the HickoryDNS auth servers support DoT it should start upgrading its requests to use DoT instead of Do53 when querying those servers. We can observe this by making recursive queries and interrogating the traffic that arrives at the auth server. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>