dnsmasq: a resolver tool and event (ADR 0044/0046)

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.
2026-09-04 10:24:03 +02:00
parent 8f8e0153b1
commit d59649de0a
6 changed files with 156 additions and 0 deletions
@@ -0,0 +1,31 @@
+// dnsmasq's tools — a resolver's two useful questions: what does it answer, and does it answer a
+// given name. Moved into the module (novox/hq ADR 0044); the mesh serves them through the sdk.
+
+import { registerModuleTools, type ToolDefinition } from "@novox/mesh-sdk/tools";
+import { DnsmasqClient } from "../client.js";
+
+export function getDnsmasqTools(dnsmasq: DnsmasqClient): ToolDefinition[] {
+  return [
+    {
+      name: "dnsmasq_names",
+      description: "The mesh names this node's resolver answers — each a machine and everything under it.",
+      input: {},
+      run: async () => ({ names: await dnsmasq.answeredNames() }),
+    },
+    {
+      name: "dnsmasq_resolve",
+      description: "Resolve a mesh name through this node's own resolver — the check that wildcard-resolution answers.",
+      input: { name: { type: "string", description: "a name to resolve, e.g. plex.anchor.internal" } },
+      run: async (args) => {
+        const name = String(args.name);
+        try {
+          return { name, addresses: await dnsmasq.resolve(name) };
+        } catch (err) {
+          return { name, addresses: [], error: err instanceof Error ? err.message : String(err) };
+        }
+      },
+    },
+  ];
+}
+
+registerModuleTools("dnsmasq", (env) => getDnsmasqTools(DnsmasqClient.fromEnv(env)));