dnsmasq's public upstream resolvers are config values, defaulting to the two it always used
mesh/delivery merged: source.main moved to novox/mesh-catalog@94805575379f
mesh/check checking c88be88ccf2f on 94805575379f

The two server lines were literals in the template, so changing an upstream needed a build. They are now the config keys upstream-resolver-first (1.1.1.1) and upstream-resolver-second (8.8.8.8), placed with ${config:...}; the service already restarts on its config file. no-resolv and every other line stay.

Claude-Session: https://claude.ai/code/session_01NcbgfFfQ4Z9UE5jK32PmE5
This commit is contained in:
2026-11-08 23:48:59 +01:00
parent 53d173aa7d
commit c88be88ccf
3 changed files with 59 additions and 3 deletions
+16
View File
@@ -38,6 +38,22 @@
"dnsmasq_names",
"dnsmasq_resolve"
],
"config": {
"upstream-resolver-first": {
"type": "string",
"description": "The first public resolver this resolver forwards to for every name that is not the mesh's own, as an IP address. It is placed as a server line beside no-resolv, so it must never be an address that resolves through this machine; both upstreams should validate DNSSEC, since the authenticated-data bit is passed down (ADR 0194, ADR 0223). Set per node or for the whole mesh.",
"trusted": false,
"pattern": "^[0-9A-Fa-f.:]+$",
"default": "1.1.1.1"
},
"upstream-resolver-second": {
"type": "string",
"description": "The second public resolver this resolver forwards to, as an IP address, tried beside the first so one upstream being down does not stop name resolution. The same rules as upstream-resolver-first.",
"trusted": false,
"pattern": "^[0-9A-Fa-f.:]+$",
"default": "8.8.8.8"
}
},
"listens": [
{
"name": "dns-udp",