Files
hq/04-ISSUES/079-every-machine-is-named-twice-over/01-diagnosis.md
T

13 lines
819 B
Markdown

# Diagnosis — 2026-09-22
1. The control plane collects every placed machine's name and address for a resolution keyed by
the internal name (`homer.internal`), because that is the map every container is given as its
hosts. The facts that render the hosts file and the resolver's zones took the same map as bare
names and appended `.internal` to each — their unit tests fed them bare names and passed.
2. Fixed in the facts: a name is read as either form, and each machine is written once as
`<machine>.internal` with its bare name beside it. A test feeds both keyings and holds the files
equal, and holds the zones free of a doubled suffix.
**Located in:** the facts. Not a decision. Proven by the unit test and by the large mesh bed's name
tests, once its controller image is rebuilt from the fix.