Title: DNS resolution fails on macOS for domains available via both private and public DNS (e.g., AWS MySQL databases)

[tissoni]

Hi NetBird team,

I'm experiencing a DNS resolution issue that occurs only on macOS. This happens across all versions of the NetBird client I’ve tested — including the latest — and it does not occur on Linux or Windows.

Importantly, this issue affects all users in my organization who are using macOS, not just a specific machine or user — confirming it's a broader platform-level issue.

Issue Description On macOS, when connected to a NetBird network, domains that have both private and public DNS records (e.g., MySQL database endpoints) often fail to resolve, or resolve incorrectly to a public IP address.

For example, if I try to connect to a MySQL database using DBeaver, the hostname fails to resolve. However:

If I run host my-db.domain.com in the macOS terminal, it resolves to a private IP.

If I copy that IP and paste it into DBeaver instead of the hostname, the connection works perfectly.

This behavior does not happen on Linux or Windows, where using the hostname in DBeaver works as expected and resolves to the correct private IP via NetBird.

Steps to Reproduce Connect to a NetBird network on macOS.

Open a terminal and run: host my-db.domain.com → it resolves to the correct private IP.

Open DBeaver, enter my-db.domain.com as the hostname → connection fails.

Enter the resolved IP manually into DBeaver → connection succeeds.

Repeat the same process on Linux or Windows — hostname resolution works and the connection succeeds without issues.

Environment OS: macOS (tested on multiple versions)

NetBird Client: Multiple versions tested — issue persists

Users affected: All macOS users in our organization

DNS Setup: Default NetBird DNS configuration

Tool used for testing: DBeaver (MySQL connection)

Expected Behavior Hostnames with private DNS records should resolve correctly via NetBird on macOS, just like they do on Linux and Windows — and should work when used directly in tools like DBeaver.

Let me know if you'd like logs or further testing (e.g., dig, scutil --dns, or verbose output from DBeaver).

Thanks for your support and for building such a great tool!