Extra DNS labels are not possible to set from dashboard #2146

Open
opened 2025-11-20 07:04:46 -05:00 by saavagebueno · 1 comment
Owner

Originally created by @AbsurdlySuspicious on GitHub (Aug 1, 2025).

Describe the problem

Setting extra dns labels is only possible via netbird up, which as far as I understand will require creating new setup key, and will lead to peer IP address change, reconnect with downtime, etc.

To Reproduce

N/A

Expected behavior

DNS labels can be updated dynamically via dashboard

Are you using NetBird Cloud?

Self-hosted

NetBird version

0.51.2

Is any other VPN software installed?

No

Debug output

N/A

Screenshots

N/A

Additional context

N/A

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @AbsurdlySuspicious on GitHub (Aug 1, 2025). **Describe the problem** Setting extra dns labels is only possible via `netbird up`, which as far as I understand will require creating new setup key, and will lead to peer IP address change, reconnect with downtime, etc. **To Reproduce** N/A **Expected behavior** DNS labels can be updated dynamically via dashboard **Are you using NetBird Cloud?** Self-hosted **NetBird version** 0.51.2 **Is any other VPN software installed?** No **Debug output** N/A **Screenshots** N/A **Additional context** N/A **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [x] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 07:04:46 -05:00
Author
Owner

@gza commented on GitHub (Oct 1, 2025):

Also:

  • On big setup with multiple teams, granting to a setup key the right to set any DNS label is a security issue:
    • By mistake or maliciously, one can get the traffic that was supposed to be sent to another service.
    • I would recommend in the "Setup Keys" UI to allow to set a kind of wildcard/regexp to limit which DNS label can be set later by the key user.
  • On non-Kube environment, the deployment of a new service with a new DNS label requires to change the key and cut the VPN for a moment.
@gza commented on GitHub (Oct 1, 2025): Also: - On big setup with multiple teams, granting to a setup key the right to set any DNS label is a security issue: - By mistake or maliciously, one can get the traffic that was supposed to be sent to another service. - I would recommend in the "Setup Keys" UI to allow to set a kind of wildcard/regexp to limit which DNS label can be set later by the key user. - On non-Kube environment, the deployment of a new service with a new DNS label requires to change the key and cut the VPN for a moment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2146