The mesh's resolver is more than config after all. Tools: dnsmasq_names (what this node answers, from the generated wildcard file) and dnsmasq_resolve (resolve a name through this node's own resolver — the check that wildcard-resolution actually answers). Event: it watches the wildcard file and emits module.dnsmasq.name.added/.removed as machines' names become resolvable here — DNS having propagated to this node, distinct from the mesh's node.* events. Typechecks; manifest parses.
10 lines
339 B
JSON
10 lines
339 B
JSON
{
|
|
"name": "@novox/module-dnsmasq",
|
|
"version": "0.1.0",
|
|
"description": "dnsmasq — the mesh's resolver: answers wildcard node names. Its tools and events live here.",
|
|
"type": "module",
|
|
"private": true,
|
|
"dependencies": { "@novox/mesh-sdk": "^0.1.0" },
|
|
"devDependencies": { "@types/node": "^22.0.0", "typescript": "^5.6.0" }
|
|
}
|