You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Netbird client adds its domain as a search domain in /etc/resolv.conf. That's all good and fine. But many applications go through all search domains when trying to resolve an address. That means that e.g. a query for ww.google.com will hit the local Netbird resolver with www.google.com.netbird.cloud. Netbird then returns an empty A record with a NOERROR flag.
The application then stops lookup with "address not found" or similar.
The problem
The Netbird client adds its domain as a
search domain
in/etc/resolv.conf
. That's all good and fine. But many applications go through all search domains when trying to resolve an address. That means that e.g. a query forww.google.com
will hit the local Netbird resolver withwww.google.com.netbird.cloud
. Netbird then returns an empty A record with aNOERROR
flag.The application then stops lookup with "address not found" or similar.
(I replaced my custom domain with "netbird.cloud")
If the local Netbird resolver would return NXDOMAIN, the application would continue its lookup. Which it absolutely should do!
To Reproduce
See above.
Expected behavior
The local Netbird resolver should return
NXDOMAIN
when no valid record is found.Are you using NetBird Cloud?
Self-hosted
NetBird version
0.27.3
NetBird status -d output:
Not applicable
Screenshots
Not applicable
Additional context
Anything I forgot to mention?
The text was updated successfully, but these errors were encountered: