netbird conflicts with adguardhome on ubuntu 22 server

[joshymg]

Describe the problem

Server already running adguardhome (docker), and everything works. Later I installed netbird, and that makes adguardhome fail on port 53 conflict.

To Reproduce

1. on the adguardhome machine: netbird installed, connected once, then 'netbird down'
2. Self hosted netbird management server, with DNS feature enabled, and nameserver address pointing to the netbird peer IP where I am running adguardhome.
3. 'netbird up' on the adguard host. adguardhome docker exits. Restarting the docker also not working.
4. 'netbird down' on the adguard host. Starting adguardhome docker succeeds.

Expected behavior

netbird client should not impact adguardhome dns server.

Are you using NetBird Cloud?

self-hosted netbird-ce .

NetBird version

netbird 0.27.3

[joshymg]

I think I spoke too soon!!
On a detailed check, it was my custom dns config in netplan config seems to be the cause.
The nameserver entry was set to my lan router IP instead of 127.0.0.1, while I was testing something else. Reverted it, then 'netplan apply'; all good now. Thanks.

[joshymg]

I have tried many ways to fix the issue. My observations:

1. On reboot, adguardhome docker starts okay.
2. Once the netbird service starts, that docker exits. Can see error related to 0.0.0.0:53 port not available.
3. 'netbird down, start the docker manually, all okay.
4. Disable netbird service, and, reboot.
5. adguardhome docker start for a moment, then exits, error: port conflict.
6. added 'ExecStartPre=/bin/sleep 30' to /etc/systemd/system/netbird.service, then reboot.
7. Same result as step 5.
8. If I disable 'Nameserver' on the management server/DNS/Nameservers page, all works normal.

Looking for ideas to fix this.

[lixmal]

Have you looked into the --dns-resolver-address CLI flag or NB_DNS_RESOLVER_ADDRESS env var: https://docs.netbird.io/how-to/cli#up

[joshymg]

For the time being I have tweaked the Nameserver - Distribution groups, and Access policies, and made it to work. In short, the DNS will not be applied to the adguardhome peer.
Not sure, if that made it work!!!
Will try for a few days and see.

[bigmehmet]

For the time being I have tweaked the Nameserver - Distribution groups, and Access policies, and made it to work. In short, the DNS will not be applied to the adguardhome peer. Not sure, if that made it work!!! Will try for a few days and see.

Thanks for the help,
I added adguard host to a group and disabled dns management for that group,
Now it works,
TY

[sunjam]

So this can be closed?

[nazarewk]

Hello @joshymg,

We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version.

Could you please confirm if the issue is still there?

We may close this issue temporarily if we don't hear back from you within 2 weeks, but feel free to reopen it with updated information.

Thanks for your contribution to improving the project!

[joshymg]

Yes, this issue is resolved using the distribution group and access policy work around.

…

On Mon, 28 Apr 2025 at 9:06 PM, Krzysztof Nazarewski (kdn) < ***@***.***> wrote: *nazarewk* left a comment (netbirdio/netbird#1859) <#1859 (comment)> Hello @joshymg <https://github.com/joshymg>, We're currently reviewing our open issues and would like to verify if this problem still exists in the latest NetBird version <https://github.com/netbirdio/netbird/releases>. Could you please confirm if the issue is still there? We may close this issue temporarily if we don't hear back from you within *2 weeks*, but feel free to reopen it with updated information. Thanks for your contribution to improving the project! — Reply to this email directly, view it on GitHub <#1859 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AISL2XIP7GRYVIPOIS4QWTT23ZDHFAVCNFSM6AAAAAB4AXTSWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZVGY3DGMJVGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>