dnsmasq: the operator's own names have a home the mesh never rewrites
A workstation's job includes names that are neither a mesh machine nor a routed name (novox/hq 122): shanks carries 13 Mediahuis entries in /etc/hosts, and mesh-wireguard replaces /etc/hosts whole when taken — so without this they vanish, and the take gates the node. Two homes, neither the mesh's to own: conf-dir=/etc/dnsmasq.d/,*.conf (drop-in directives, HAL's dnsmasq-app used exactly this) and addn-hosts=/etc/hosts.local (plain host lines). The mesh creates and rewrites neither; a machine with none loses nothing. The migration moves such names here BEFORE the /etc/hosts take, closing the window.
This commit is contained in:
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user