dnsmasq: answer a container's query, which arrives on the runtime's bridge #176

Merged
jschoubben merged 1 commits from fix/110-the-resolver-answers-a-container into main 2026-09-30 12:31:30 +00:00
Owner

novox/hq issue 110. With interface=mesh0 alone dnsmasq dropped every query from a container, silently, on every machine. listen-address names the address instead, so the bridge the query arrives on no longer matters.

novox/hq issue 110. With interface=mesh0 alone dnsmasq dropped every query from a container, silently, on every machine. listen-address names the address instead, so the bridge the query arrives on no longer matters.
jschoubben added 1 commit 2026-09-30 12:31:27 +00:00
dnsmasq admits a query by the interface it arrives on when told interface=,
and by the address it is sent to when told listen-address=. A container's
query is sent to the machine's private address but arrives on docker0, so
interface=mesh0 dropped it silently on every machine (novox/hq issue 110).
Name the address, not the interface.
jschoubben merged commit 7ab522ba31 into main 2026-09-30 12:31:30 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#176