Issues 111 and 112: the resolver was told the wrong set of names, twice over #98

Merged

jschoubben merged 1 commits from issues/111-112-the-resolver-was-told-the-wrong-names into main

2026-09-23 23:32:42 +00:00

Author	SHA1	Message	Date
jschoubben	f704e2ca64	Issues 111 and 112: the resolver was told the wrong set of names, twice over 111, resolved: the map the control plane hands a resolution holds the machines and the names the mesh merely serves, and the resolver's zones were given both — inventing names under a suffix it answers authoritatively for. 112, open: adopting a tunnel gives the mesh the peers' addresses and none of their names, so taking the resolver before they enrol stops three machines resolving at all. Both found by reading the plan before pushing it.	2026-09-24 01:32:04 +02:00

Author

SHA1

Message

Date

jschoubben

f704e2ca64

Issues 111 and 112: the resolver was told the wrong set of names, twice over

111, resolved: the map the control plane hands a resolution holds the machines and the
names the mesh merely serves, and the resolver's zones were given both — inventing names
under a suffix it answers authoritatively for. 112, open: adopting a tunnel gives the mesh
the peers' addresses and none of their names, so taking the resolver before they enrol
stops three machines resolving at all.

Both found by reading the plan before pushing it.

2026-09-24 01:32:04 +02:00