A domain-based Network Resource does not register itself with operating system #1727

Open
opened 2025-11-20 06:05:32 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @nazarewk on GitHub (Mar 18, 2025).

Describe the problem

basically the domain-based Network Resource:

  1. properly registers in a routing table after it gets resolved by the DNS, but it does not get to this due to point 2
  2. nothing is registering the domain with system's resolver so it cannot get to point 1) without additional help (point 3)
  3. a workaround is to create a dummy Nameserver in the management for the domain

the only reason it works on Linux clients is due to how resolved behaves with +DefaultRoute, normally it should not work here either

I am pretty sure this should be implemented/fixed

To Reproduce

  1. create a Network with a domain Resource
  2. the selected domain does not get registered with operating system's resolver

Expected behavior

the domain defined in a Network Resource is poperly registered with operating system's DNS resolver

Are you using NetBird Cloud?

Yes

NetBird version

n/a

Is any other VPN software installed?

no

Debug output

n/a

Screenshots

n/a

Additional context

public slack thread https://netbirdio.slack.com/archives/C02KHAE8VLZ/p1741875626437989

Have you tried these troubleshooting steps?

  • 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 @nazarewk on GitHub (Mar 18, 2025). **Describe the problem** basically the domain-based Network Resource: 1. properly registers in a routing table after it gets resolved by the DNS, but it does not get to this due to point 2 2. nothing is registering the domain with system's resolver so it cannot get to point 1) without additional help (point 3) 3. a workaround is to create a dummy Nameserver in the management for the domain the only reason it works on Linux clients is due to how resolved behaves with +DefaultRoute, normally it should not work here either I am pretty sure this should be implemented/fixed **To Reproduce** 1. create a Network with a `domain` Resource 2. the selected `domain` does not get registered with operating system's resolver **Expected behavior** the `domain` defined in a Network Resource is poperly registered with operating system's DNS resolver **Are you using NetBird Cloud?** Yes **NetBird version** n/a **Is any other VPN software installed?** no **Debug output** n/a **Screenshots** n/a **Additional context** public slack thread https://netbirdio.slack.com/archives/C02KHAE8VLZ/p1741875626437989 **Have you tried these troubleshooting steps?** - [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 bugnetworkingdns labels 2025-11-20 06:05:33 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#1727