[GH-ISSUE #1349] Add support for CNAME in Network Routes #2249

Open
opened 2026-08-05 00:46:06 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Thunderbottom on GitHub (Nov 30, 2023).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1349

Is your feature request related to a problem? Please describe.
Currently, there's no way to add CNAME to a network route entry in Netbird. This is particularly useful in cases where the infrastructure is hosted by a service provider, eg. AWS, Azure, et al. Or even in cases where the network host uses dynamic DNS.

As a workaround for this, currently, the entire VPC subnet that the ALB is a part of needs to be added as a network route, which is sub-optimal and does not allow granular control over permissions. For example, adding a network route for the subnet 10.0.0.0/16 (considering the ALB is in the same subnet) and distributing it to the peers in group-xyz gives the people of that group access to the entire subnet (instead of just the ALB), which might be a huge security issue for a lot of organizations.

And since Netbird cannot be installed on resources like an ALB, the only way right now is to whitelist the subnet the ALB is spawned in.

Describe the solution you'd like
There needs to be a way to add CNAME entries to a network route. This can be separate to the "Network Range CIDR" that's currently handled by Netbird as an alternate option for the CIDR range.

Describe alternatives you've considered
Currently the only other option is to whitelist an entire VPC subnet. Which, again, would be a security nightmare for a lot of organizations.

Originally created by @Thunderbottom on GitHub (Nov 30, 2023). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1349 **Is your feature request related to a problem? Please describe.** Currently, there's no way to add `CNAME` to a network route entry in Netbird. This is particularly useful in cases where the infrastructure is hosted by a service provider, eg. AWS, Azure, et al. Or even in cases where the network host uses dynamic DNS. As a workaround for this, currently, the entire VPC subnet that the ALB is a part of needs to be added as a network route, which is sub-optimal and does not allow granular control over permissions. For example, adding a network route for the subnet `10.0.0.0/16` (considering the ALB is in the same subnet) and distributing it to the peers in `group-xyz` gives the people of that group access to the entire subnet (instead of just the ALB), which might be a huge security issue for a lot of organizations. And since Netbird cannot be installed on resources like an ALB, the only way right now is to whitelist the subnet the ALB is spawned in. **Describe the solution you'd like** There needs to be a way to add `CNAME` entries to a network route. This can be separate to the "Network Range CIDR" that's currently handled by Netbird as an alternate option for the CIDR range. **Describe alternatives you've considered** Currently the only other option is to whitelist an entire VPC subnet. Which, again, would be a security nightmare for a lot of organizations.
saavagebueno added the feature-requestclientmanagement-servicedns labels 2026-08-05 00:46:06 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#2249