[GH-ISSUE #5320] [Feature Request] DNS settings tied to network routes/exit nodes #10323

Open
opened 2026-08-05 01:25:27 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @kristianvld on GitHub (Feb 14, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5320

Is your feature request related to a problem? Please describe.
Yes. Current DNS settings are static and tied to hosts through Access Control Groups. However, which resources are reachable can change depending on accessible routes or networks that the host is connected to. E.g. a client like a laptop or phone might by default use the device's default DNS settings broadcasted through DHCP, which can be desirable for local resources or things like making captive portals work, but while an Exit Node is enabled, this DNS server is no longer reachable, breaking DNS on the client. Some resources or services might also be exposed on routes which can be enabled or disabled. Having DNS resolutions for these settings always being configured can be undesirable, specially if you want to point custom DNS entries to different IPs based on which route is configured/enabled for the client.

This issue is closely tied to #4025, but I believe this should be abstracted one layer higher up for all routes, not just for Exit Node routes.

Describe the solution you'd like
It would be convenient of certain DNS settings could be tied to specific routes and be applied to all hosts which this route is active for. E.g. when a Network Route/Exit Node is active (not just to be selected, but active for a Node), then these DNS settings are active as well. E.g. when a client enables an Exit Node route, the default DNS server is pointed to 1.1.1.1 instead of a local LAN IP like 192.168.1.1 which might have been broadcasted through DHCP.

Describe alternatives you've considered
Developing custom scripts to install on all clients to monitor for if a network route is enabled or not, and configure the machines DNS setting based on that. This is clunky, error prone, requires custom development and does not work on clients mobile clients.

Alternatively having a management script monitor Netbird centrally to check which Network Routes/Exit Nodes are active for routes and push DNS changes to Netbird and let Netbird distribute these DNS changes to client. This moves configuration management out of Netbird to third-party/custom scripts, which is not scalable and highly error prone.

Additional context
None.

Originally created by @kristianvld on GitHub (Feb 14, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5320 **Is your feature request related to a problem? Please describe.** Yes. Current DNS settings are static and tied to hosts through Access Control Groups. However, which resources are reachable can change depending on accessible routes or networks that the host is connected to. E.g. a client like a laptop or phone might by default use the device's default DNS settings broadcasted through DHCP, which can be desirable for local resources or things like making captive portals work, but while an Exit Node is enabled, this DNS server is no longer reachable, breaking DNS on the client. Some resources or services might also be exposed on routes which can be enabled or disabled. Having DNS resolutions for these settings always being configured can be undesirable, specially if you want to point custom DNS entries to different IPs based on which route is configured/enabled for the client. This issue is closely tied to #4025, but I believe this should be abstracted one layer higher up for all routes, not just for Exit Node routes. **Describe the solution you'd like** It would be convenient of certain DNS settings could be tied to specific routes and be applied to all hosts which this route is active for. E.g. when a Network Route/Exit Node is active (not just to be selected, but active for a Node), then these DNS settings are active as well. E.g. when a client enables an Exit Node route, the default DNS server is pointed to 1.1.1.1 instead of a local LAN IP like 192.168.1.1 which might have been broadcasted through DHCP. **Describe alternatives you've considered** Developing custom scripts to install on all clients to monitor for if a network route is enabled or not, and configure the machines DNS setting based on that. This is clunky, error prone, requires custom development and does not work on clients mobile clients. Alternatively having a management script monitor Netbird centrally to check which Network Routes/Exit Nodes are active for routes and push DNS changes to Netbird and let Netbird distribute these DNS changes to client. This moves configuration management out of Netbird to third-party/custom scripts, which is not scalable and highly error prone. **Additional context** None.
saavagebueno added the feature-request label 2026-08-05 01:25:27 -04:00
Author
Owner

@Deniom3 commented on GitHub (Feb 28, 2026):

I'm also interested in this functionality. My scenario is that different IP addresses need to be linked to the same domain in a zone in different networks. Currently, there's no way to duplicate a DNS zone and create another record for a different group. A possible solution would be to remove the restriction on re-adding the root record to the DNS zone.

<!-- gh-comment-id:3977893929 --> @Deniom3 commented on GitHub (Feb 28, 2026): I'm also interested in this functionality. My scenario is that different IP addresses need to be linked to the same domain in a zone in different networks. Currently, there's no way to duplicate a DNS zone and create another record for a different group. A possible solution would be to remove the restriction on re-adding the root record to the DNS zone.
Author
Owner

@greg-court commented on GitHub (Mar 25, 2026):

+1 on this. In practice the right DNS depends on the route/exit node being used, not just the client group. Static DNS per client group gets awkward fast in multi-site setups. DNS is still the weakest part of NetBird for me right now in an otherwise great product.

<!-- gh-comment-id:4125576760 --> @greg-court commented on GitHub (Mar 25, 2026): +1 on this. In practice the right DNS depends on the route/exit node being used, not just the client group. Static DNS per client group gets awkward fast in multi-site setups. DNS is still the weakest part of NetBird for me right now in an otherwise great product.
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10323