From c8af8d5eb1ce17e6c7cfac12b9a7cf5ca3c73e72 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 5 Oct 2026 21:18:49 +0200 Subject: [PATCH] Issue 258: resolved --- .../00-report.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/04-ISSUES/258-every-machine-bound-the-resolver-to-itself/00-report.md b/04-ISSUES/258-every-machine-bound-the-resolver-to-itself/00-report.md index d22c268..32f3c5f 100644 --- a/04-ISSUES/258-every-machine-bound-the-resolver-to-itself/00-report.md +++ b/04-ISSUES/258-every-machine-bound-the-resolver-to-itself/00-report.md @@ -1,8 +1,8 @@ --- -status: located +status: resolved opened: 2026-10-05 located-in: [mesh-controller] -fixed-by: novox/mesh-controller#59 +fixed-by: novox/mesh-controller#59 (4b382ce) amended-design: --- @@ -45,3 +45,9 @@ This is checked by three resolve tests in mesh-controller: - a holder here still answers here. The tests fail without the fix. + +## Verified + +2026-10-05, after the fix rolled out: all four machines' resolver configuration names the anchor's +resolver first and the public one second. Each resolves the mesh's machine names, a wildcard name +under a machine, and a public name.