PP-284 earlier hands-on check record, October 3, 2026

Historical record. This page documents a small check run on October 3, 2026, before Practical Picks adopted its research-only method later that day. We keep it as dated evidence; it does not describe current testing, and the comparison's recommendations now rest on public sources. Notes added October 19, 2026: named-checkzone 9.18.39, used here, predates ISC's May 20, 2026 fix (BIND 9.18.49 and 9.20.23) for a missing-glue check that could be skipped when a name server had already drawn an extra-AAAA-glue warning; these files contain no AAAA glue, so that condition did not arise. kzonecheck 3.3.4 predates Knot 3.4.7's June 2025 fix for a false missing-glue warning. The SHA-256 below is for Codeberg's generated v0.11.0 tag archive; DNS-OARC's separate release tarball has a different checksum, listed in its release notes.

Run October 3, 2026 on Ubuntu 24.04 amd64. All names use the invented pp284.test. zone. The commands read local text files; they do not query DNS or upload a zone.

Synthetic zone files used

How the October 3 check was run (historical)

Save the five zone files and four scripts below in the same directory. On a comparable Ubuntu 24.04 amd64 host with apt-get, dpkg-deb, Python 3, GCC, curl, tar and SHA-256 tools, run:

PP284_WORKDIR="$PWD/pp284-work" bash replay.sh

Replay wrapper · Ubuntu package runner · Current validns builder · Current validns runner · Full method text

The wrapper downloads exact Ubuntu package versions with apt-get download, extracts them into the task directory, then fetches the official validns v0.11.0 archive. It verifies SHA-256 56162037254d488136081f1c5e56f9946bdda5100d3da4873fd58691c9188ce7 before building the 60 listed source files with local Judy/OpenSSL development files. It runs the original optional-policy check, the calibrated package comparison, and the current validns comparison. No package is installed. Host runtime libraries must already be available.

The original downloads totaled about 4.1 MB and the task-local extraction/build footprint was about 25 MB. Package availability and host libraries can change. The direct GCC build is a bounded test binary, not an upstream package or full test suite. Retained JSON contains original absolute paths; replayed paths will differ.

Captured output, October 3, 2026