Name based routes are ignored with client 0.36.x on MacOS

[samroweemployinc]

We're running 0.36.5 on the coordinator and peers and if our MacOS users upgrade to 0.36.x they're no longer able to use name based routes. We haven't converted to Networks yet. Downgrading to 0.34.1 restores the functionality. Our peers aren't publicly available, so the connections are all relayed. Linux 0.36.5 clients seem to work fine.

To Reproduce

Steps to reproduce the behavior:

1. Create a name-based-route
2. Use 0.36.x on MacOS and try to go to that route. We've used a homebrew-installed tcptraceroute to test the path. After downgrading to 0.34.1 the traceroute will go over Netbird.

Expected behavior

Name-based routes should continue to function.

Are you using NetBird Cloud?

Self-hosted

NetBird version

On the clients: 0.36.5 and 0.36.3 were tested.
On the peers and coordinator: 0.36.5

[lixmal]

Is this setting enabled?

If yes, you will need to ensure that the routing peer can resolve the domain and that the routing client has a DNS server assigned.

Otherwise turn the setting off.

[samroweemployinc]

@lixmal Thanks for the reply. Does that mean that even though that setting is under a heading that says "Networks" it applies to old-school Routes as well?

The docs aren't super clear on what you mean by "DNS server assigned." Does that mean the peer(s) need a Netbird DNS Server in its group and not just have working DNS in its OS?

[lixmal]

@lixmal Thanks for the reply. Does that mean that even though that setting is under a heading that says "Networks" it applies to old-school Routes as well?

Yes, it's a setting for the client. Networks and Network Routes are the same thing from the point of view of the client.

The docs aren't super clear on what you mean by "DNS server assigned." Does that mean the peer(s) need a Netbird DNS Server in its group and not just have working DNS in its OS?

DNS has to go through Netbird for the routes to work. Ideally you assign a default DNS server (no specific match domains defined), unless you want to keep the match domain list up-to-date with the defined dns routes.