[GH-ISSUE #4948] FQDN support in ACLs #10164

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

Originally created by @j007bond007 on GitHub (Dec 14, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4948

Is your feature request related to a problem? Please describe.
NetBird only seems to allow entering IP/Port information, but yet claims Zero-Trust. To align with other zero trust solutions, it would be beneficial to have the ability to create ACLs based on hostnames/domain names/FQDNs so if someone enters app.domain.com or app2.domain.com you can differentiate them in ACLs if they point to the same IP (E.g. shared host, reverse proxies, etc.).

Describe the solution you'd like
This would involve NetBird looking further up the OSI model, not just converting the hostname to an IP but looking at host headers for anything travelling through the NetBird network to ensure it matches the ACL. This would take the security to the next level and allow more granular policies.

Describe alternatives you've considered
Application based auth (Layer 7), but this does not protect at Layer 4 and can introduce security vulnerabilities at the application layer.

Additional context
For reference, you can see OpenZiti which allows such a feature, or paid commercial ZTNA software that allows this.

Originally created by @j007bond007 on GitHub (Dec 14, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4948 **Is your feature request related to a problem? Please describe.** NetBird only seems to allow entering IP/Port information, but yet claims Zero-Trust. To align with other zero trust solutions, it would be beneficial to have the ability to create ACLs based on hostnames/domain names/FQDNs so if someone enters app.domain.com or app2.domain.com you can differentiate them in ACLs if they point to the same IP (E.g. shared host, reverse proxies, etc.). **Describe the solution you'd like** This would involve NetBird looking further up the OSI model, not just converting the hostname to an IP but looking at host headers for anything travelling through the NetBird network to ensure it matches the ACL. This would take the security to the next level and allow more granular policies. **Describe alternatives you've considered** Application based auth (Layer 7), but this does not protect at Layer 4 and can introduce security vulnerabilities at the application layer. **Additional context** For reference, you can see OpenZiti which allows such a feature, or paid commercial ZTNA software that allows this.
saavagebueno added the feature-request label 2026-08-05 01:24:50 -04:00
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#10164