ADR 0191: the mesh's resolver holds only the mesh's own names; a public name resolves publicly

Publishing every routed public name at a private address turned ace's LAN-facing resolver into an outage for non-members: a phone got the control-node's tunnel address for the mail server. Routes have internal names since 0151 and the proxy certifies public names publicly, so nothing needs the private answer. Narrows 0066 and 0151; amends connectivity §2 and §5.
2026-10-03 15:11:45 +02:00
parent 22e96e5bc7
commit e5e6e56ecf
5 changed files with 160 additions and 13 deletions
@@ -222,6 +222,7 @@ python3 00-META/checks/index.py            fail if stale
 - **0126** — [A module declares its own seats; the mesh reserves its own](0126-a-module-declares-its-own-seats.md)
 - **0148** — [The mesh's names are resolved, not copied into every container](0148-the-meshs-names-are-resolved-not-copied-into-containers.md)
 - **0151** — [A route's internal name is composed under the node that serves it](0151-a-routes-internal-name-is-composed-under-the-node-that-serves-it.md)
+- **0191** — [The mesh's resolver holds only the mesh's own names; a public name resolves publicly](0191-the-meshs-resolver-holds-only-the-meshs-own-names.md)

 ### What runs on them, and how it gets there