Just sharing this on the forum as well for additional visibility.
opened 08:18AM - 30 Jul 25 UTC
bug
client
triage-needed
**Describe the problem**
The forceful setting of netbird dns resolver cause iss… ue on some system
First of all: not all systems needs to have enabled the netbird dns resolver, so the decision to force it enabled no matter what is configured on the dns settings is not the most clever one.
Secondly on some system the config is not applied resulting in the total break of dns resolution (that is: the nameserver row in resolv.conf reports invalid ip/hostname).
Thirdly: on some mail relay system that rely on rbl checking via dns it reports bogus dns query with the reject of mails due to misleading rbl query.
Currently there is not a way to disable the auto management of configuration, even if the peer group is added to the exclusion list.
I have been using netbird for less than a month and I’m having trouble differentiating changes I’ve made vs breaking changes from upstream.
Xeravax
September 10, 2025, 10:13am
2
I tend to go across and check “what changes where made, do they apply to me and do I need to change anything in the setup.env”. From there I can apply whatever’s needed to update Netbird (at least on the self-hosted aspect)