fix(netbird-server): keep the host mesh client out of DNS #1427

Merged

k.renner merged 1 commits from fix/netbird-controller-disable-dns into main

2026-10-22 19:56:52 +00:00

Author	SHA1	Message	Date
claude-botandClaude Opus 5.5	29c299c0fe	fix(netbird-server): keep the host mesh client out of DNS ci/woodpecker/pr/ci-scripts-test Pipeline was successful Details The controller's own NetBird client registered ~renner.uno in systemd-resolved, pointing at the kube-dns-lb nameserver group, which is unreachable from this peer. Every *.renner.uno lookup on the host returned SERVFAIL, and Uptime Kuma, resolving through Docker's embedded DNS and the host stub, marked all HTTP monitors DOWN after the 2026-10-22 update-os reboot. The role now reconnects the client with --disable-dns when its config has DNS management enabled. The flag is only honoured on a fresh up, so the task runs netbird down + up; it is a no-op once disableDns is true. Applied live and verified 2026-10-22 before this commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 21:55:11 +02:00

Author

SHA1

Message

Date

claude-botandClaude Opus 5.5

29c299c0fe

fix(netbird-server): keep the host mesh client out of DNS

ci/woodpecker/pr/ci-scripts-test Pipeline was successful

Details

The controller's own NetBird client registered ~renner.uno in
systemd-resolved, pointing at the kube-dns-lb nameserver group, which is
unreachable from this peer. Every *.renner.uno lookup on the host returned
SERVFAIL, and Uptime Kuma, resolving through Docker's embedded DNS and the
host stub, marked all HTTP monitors DOWN after the 2026-10-22 update-os
reboot.

The role now reconnects the client with --disable-dns when its config has
DNS management enabled. The flag is only honoured on a fresh up, so the
task runs netbird down + up; it is a no-op once disableDns is true.
Applied live and verified 2026-10-22 before this commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-22 21:55:11 +02:00