[GH-ISSUE #1859] netbird conflicts with adguardhome on ubuntu 22 server #3541

Closed
opened 2026-08-05 00:52:57 -04:00 by saavagebueno · 11 comments
Owner

Originally created by @joshymg on GitHub (Apr 17, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/1859

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

Originally created by @joshymg on GitHub (Apr 17, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/1859 **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`
saavagebueno added the clientwaiting-feedbackdns labels 2026-08-05 00:52:57 -04:00
Author
Owner

@joshymg commented on GitHub (Apr 17, 2024):

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.

<!-- gh-comment-id:2062881209 --> @joshymg commented on GitHub (Apr 17, 2024): 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.
Author
Owner

@joshymg commented on GitHub (Apr 18, 2024):

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.

<!-- gh-comment-id:2065628170 --> @joshymg commented on GitHub (Apr 18, 2024): 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.
Author
Owner

@lixmal commented on GitHub (Apr 19, 2024):

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

<!-- gh-comment-id:2066110096 --> @lixmal commented on GitHub (Apr 19, 2024): 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
Author
Owner

@joshymg commented on GitHub (Apr 19, 2024):

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.

<!-- gh-comment-id:2066216115 --> @joshymg commented on GitHub (Apr 19, 2024): 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.
Author
Owner

@bigmehmet commented on GitHub (Jun 27, 2024):

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

<!-- gh-comment-id:2194398176 --> @bigmehmet commented on GitHub (Jun 27, 2024): > 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
Author
Owner

@sunjam commented on GitHub (Oct 5, 2024):

So this can be closed?

<!-- gh-comment-id:2395082833 --> @sunjam commented on GitHub (Oct 5, 2024): So this can be closed?
Author
Owner

@nazarewk commented on GitHub (Apr 28, 2025):

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!

<!-- gh-comment-id:2835663154 --> @nazarewk commented on GitHub (Apr 28, 2025): Hello @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!
Author
Owner

@joshymg commented on GitHub (Apr 28, 2025):

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)
https://github.com/netbirdio/netbird/issues/1859#issuecomment-2835663154

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
https://github.com/netbirdio/netbird/issues/1859#issuecomment-2835663154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AISL2XIP7GRYVIPOIS4QWTT23ZDHFAVCNFSM6AAAAAB4AXTSWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZVGY3DGMJVGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

<!-- gh-comment-id:2837147372 --> @joshymg commented on GitHub (Apr 28, 2025): 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) > <https://github.com/netbirdio/netbird/issues/1859#issuecomment-2835663154> > > 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 > <https://github.com/netbirdio/netbird/issues/1859#issuecomment-2835663154>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AISL2XIP7GRYVIPOIS4QWTT23ZDHFAVCNFSM6AAAAAB4AXTSWKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMZVGY3DGMJVGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >
Author
Owner

@jotbed commented on GitHub (Jul 8, 2025):

I Just installed Netbird on a Adguard Instance. I had to role back. AdGuard will not start.

<!-- gh-comment-id:3048091246 --> @jotbed commented on GitHub (Jul 8, 2025): I Just installed Netbird on a Adguard Instance. I had to role back. AdGuard will not start.
Author
Owner

@nazarewk commented on GitHub (Jul 9, 2025):

@jotbed @joshymg I might be wrong, but from what I understood, AdGuard container is trying to listen on all possible interfaces on all of the ports (including 53). Which would make sense for "ease of use" if it were the only thing running on the machine, but is otherwise far from best practice and will interfere with a lot more systems than just NetBird.

I would suggest you to reconfigure AdGuard to listen only on the LAN-facing interfaces and ignore the rest. You can specify by providing -p <ip>:<host-port>:<container-port>

<!-- gh-comment-id:3054037175 --> @nazarewk commented on GitHub (Jul 9, 2025): @jotbed @joshymg I might be wrong, but from what I understood, AdGuard container is trying to listen on all possible interfaces on all of the ports (including `53`). Which would make sense for "ease of use" if it were the only thing running on the machine, but is otherwise far from best practice and will interfere with a lot more systems than just NetBird. I would suggest you to reconfigure AdGuard to listen only on the LAN-facing interfaces and ignore the rest. You can specify by providing `-p <ip>:<host-port>:<container-port>`
Author
Owner

@PizzaLovingNerd commented on GitHub (Jun 5, 2026):

Closing as a configuration issue.

Exclude the AdGuard peer from NetBird DNS management through DNS Settings/distribution groups, or set a custom resolver bind address with --dns-resolver-address if another service needs port 53.

Cheers!

<!-- gh-comment-id:4636172640 --> @PizzaLovingNerd commented on GitHub (Jun 5, 2026): Closing as a configuration issue. Exclude the AdGuard peer from NetBird DNS management through DNS Settings/distribution groups, or set a custom resolver bind address with `--dns-resolver-address` if another service needs port 53. Cheers!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#3541