jschoubben c88be88ccf dnsmasq's public upstream resolvers are config values, defaulting to the two it always used ...

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

..

dnsmasq.conf

dnsmasq's public upstream resolvers are config values, defaulting to the two it always used

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

mesh.conf

dnsmasq: the drop-in no longer orders after network-online.target and its address wait is 2 s at most (cycle dropped the start at boot, issue 1126)

2026-10-28 17:00:14 +01:00