[GH-ISSUE #5726] Custom DNS zone records not distributed to clients (LocalResolver [0 records]) #10992

Open
opened 2026-08-05 01:28:01 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Yagi-Michael on GitHub (Mar 29, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5726

Description

Custom DNS zone records created in the dashboard are not distributed to clients. The zone handler is registered on the client but with 0 records.

Steps to Reproduce

  1. Self-hosted NetBird v0.67.1 (quickstart deployment)
  2. Client v0.67.0/0.67.1 on Linux with systemd-resolved
  3. Create a DNS zone gub.internal via dashboard with Distribution Group "All"
  4. Add A records (e.g., hostname sewa-prod, IP 100.79.153.212)
  5. Reconnect client: netbird down && netbird up
  6. Check client debug logs

Expected Behavior

Client logs should show LocalResolver [6 records] for the zone.

Actual Behavior

registering handler LocalResolver [0 records] with priority 75 for [gub.internal.]

The zone is registered but no records are distributed. DNS queries for sewa-prod.gub.internal fail.

Debug Log (client, full reconnect)

added reverse DNS zone: 79.100.in-addr.arpa. with 2 records
starting dns on 100.79.153.212:53
registering handler LocalResolver [0 records] with priority 75 for [netbird.selfhosted.]
registering handler LocalResolver [0 records] with priority 75 for [gub.internal.]
registering handler LocalResolver [0 records] with priority 75 for [79.100.in-addr.arpa.]
adding 2 search domains and 1 match domains. Search list: [netbird.selfhosted. gub.internal.] , Match list: [79.100.in-addr.arpa.]

Environment

  • Server: netbirdio/netbird-server:latest (v0.67.1)
  • Client: v0.67.0 and v0.67.1
  • OS: Ubuntu 24.04 (server), NixOS (client)
  • DNS manager: systemd-resolved
  • Deployment: self-hosted quickstart with nginx reverse proxy
Originally created by @Yagi-Michael on GitHub (Mar 29, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5726 ## Description Custom DNS zone records created in the dashboard are not distributed to clients. The zone handler is registered on the client but with 0 records. ## Steps to Reproduce 1. Self-hosted NetBird v0.67.1 (quickstart deployment) 2. Client v0.67.0/0.67.1 on Linux with systemd-resolved 3. Create a DNS zone `gub.internal` via dashboard with Distribution Group "All" 4. Add A records (e.g., hostname `sewa-prod`, IP `100.79.153.212`) 5. Reconnect client: `netbird down && netbird up` 6. Check client debug logs ## Expected Behavior Client logs should show `LocalResolver [6 records]` for the zone. ## Actual Behavior ``` registering handler LocalResolver [0 records] with priority 75 for [gub.internal.] ``` The zone is registered but no records are distributed. DNS queries for `sewa-prod.gub.internal` fail. ## Debug Log (client, full reconnect) ``` added reverse DNS zone: 79.100.in-addr.arpa. with 2 records starting dns on 100.79.153.212:53 registering handler LocalResolver [0 records] with priority 75 for [netbird.selfhosted.] registering handler LocalResolver [0 records] with priority 75 for [gub.internal.] registering handler LocalResolver [0 records] with priority 75 for [79.100.in-addr.arpa.] adding 2 search domains and 1 match domains. Search list: [netbird.selfhosted. gub.internal.] , Match list: [79.100.in-addr.arpa.] ``` ## Environment - Server: netbirdio/netbird-server:latest (v0.67.1) - Client: v0.67.0 and v0.67.1 - OS: Ubuntu 24.04 (server), NixOS (client) - DNS manager: systemd-resolved - Deployment: self-hosted quickstart with nginx reverse proxy
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10992