A route's internal name says where the request arrives #163

Merged
jschoubben merged 1 commits from fix/139-a-routes-internal-name-says-where-it-arrives into main 2026-09-30 12:51:17 +00:00
Owner

novox/hq ADR 0151, issues 139 and 157. The internal name composes under the node whose proxy serves the route; a routed public name is published as itself, with no .internal alias.

novox/hq ADR 0151, issues 139 and 157. The internal name composes under the node whose proxy serves the route; a routed public name is published as itself, with no .internal alias.
jschoubben added 1 commit 2026-09-30 12:51:13 +00:00
novox/hq ADR 0151 (issues 139, 157). <label>.<node>.internal is answered
by every resolver as 'anything under that node goes to that node', so
the node in a route's internal name must be the one whose proxy answers
it; composed under the consumer's own name it sent a client to a machine
with nothing listening whenever the proxy ran elsewhere. Composed under
the serving node now — the same machine wherever the proxy runs beside
the module, so nothing changes on a mesh with one hub.

A routed public name gets no .internal alias any more: the roster
publishes it as itself, once. The alias resolved and nothing served it.
jschoubben merged commit 481b1a7b05 into main 2026-09-30 12:51:17 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-controller#163