dnsmasq: the public upstream resolvers are settings, not fixed in the template #634

Merged

mesh-tools merged 1 commits from fix/dnsmasq-upstreams into main

2026-11-08 22:51:12 +00:00

Author	SHA1	Message	Date
jschoubben	c88be88ccf	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 Details 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	2026-11-08 23:48:59 +01:00

Author

SHA1

Message

Date

jschoubben

c88be88ccf

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

Details

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

2026-11-08 23:48:59 +01:00