[GH-ISSUE #4864] Peer clients seem to ignore upstream nameservers #9962

New Issue

saavagebueno · 2026-08-05T01:24:09-04:00

saavagebueno commented

2026-08-05 01:24:09 -04:00

Originally created by @TimTheOverlord on GitHub (Nov 26, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/4864

Describe the problem

I’m running a self-hosted NetBird setup (0.60.2) using Authentik as the IdP and Caddy as a reverse proxy, following the advanced self-hosting guide. I also have an AdGuard Home instance. Everything (Caddy, Authentik, NetBird, AdGuard Home) is on a single Docker host core-srv (192.168.50.16). I have a NetBird exit node on a separate host (gp-srv@192.168.50.24) I’m trying to use NetBird’s DNS features + wildcard routing so that, once peers connect, they resolve vpn.mydomain.com and all other hostnames via AdGuard.

However, after connecting to NetBird, the only DNS queries that make their way to AdGuard are LAN rewrites I've set, excluding vpn.mydomain.com, which continues to resolve to the WAN IP unless I explicitly target AdGuard with @192.168.50.16 in my domain queries. It looks like queries for this hostname, as well as all other public names, are bypassing the NetBird DNS/wildcard routing logic. I've tested this on Linux, Windows, and Android clients.

In Cloudflare, I've configured:

vpn.mydomain.com -> WAN IP

In AdGuard I've configured:

vpn.mydomain.com -> 192.168.50.16

In NetBird, I've configured the following:

Nameserver for 192.168.50.16
- Configured for all domains
- Configured for all peers
Network for MyNetwork
- Resources for 192.168.50.16/32, 192.168.50.0/24, *.mydomain.com
- Routed through gp-srv@192.168.50.24
- Configured for all peers
Policy to allow all peers to 192.168.50.16:53
Enabled the DNS wildcard routing setting

As I mentioned, the expected behavior is that once clients connect to NetBird, they use the configured Nameserver to resolve all DNS queries (vpn.mydomain.com, newegg.com, google.com all go through AdGuard in my case). The actual behavior is that after connecting to NetBird:

dig/nslookup commands using default servers on clients appear use the NetBird local resolver (127.0.0.53 for Linux, 100.99.255.254 for Windows).
Unless specifying the AdGuard instance in those dig/nslookup commands, vpn.mydomain.com always resolves to my WAN IP from the Cloudflare DNS record. When specifying the AdGuard instance in those commands, the correct IP (192.168.50.16) is resolved.
When running tcpdump -ni wt0 udp port 53 on the exit node, only requests for LAN DNS rewrites make it across the exit node, no other DNS requests come through the exit node.

Are you using NetBird Cloud?

Self-hosted NetBird.

NetBird version

0.60.2

Is any other VPN software installed?

No

Debug output

To help us resolve the problem, please attach the following anonymized status output

netbird debug for 1m -AS

Attached in a .zip
netbird.debug.454865632.zip

Additional context

I'm willing to be told I did something wrong in setting up NetBird or I'm doing something really dumb on my DNS side of things. Am I incorrect in thinking clients will adjust their DNS settings to take on nameserver configurations from the NetBird tunnel (yes, I did make sure that private DNS settings were turned off on client devices)?

Have you tried these troubleshooting steps?

Reviewed client troubleshooting (if applicable)
Checked for newer NetBird versions
[~] Searched for similar issues on GitHub (including closed ones)
Restarted the NetBird client
Disabled other VPN software
Checked firewall settings

Originally created by @TimTheOverlord on GitHub (Nov 26, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/4864 **Describe the problem** I’m running a self-hosted NetBird setup (0.60.2) using Authentik as the IdP and Caddy as a reverse proxy, following the advanced self-hosting guide. I also have an AdGuard Home instance. Everything (Caddy, Authentik, NetBird, AdGuard Home) is on a single Docker host `core-srv` (`192.168.50.16`). I have a NetBird exit node on a separate host (`gp-srv@192.168.50.24`) I’m trying to use NetBird’s DNS features + wildcard routing so that, once peers connect, they resolve `vpn.mydomain.com` and all other hostnames via AdGuard. However, after connecting to NetBird, the only DNS queries that make their way to AdGuard are LAN rewrites I've set, excluding `vpn.mydomain.com`, which continues to resolve to the WAN IP unless I explicitly target AdGuard with `@192.168.50.16` in my domain queries. It looks like queries for this hostname, as well as all other public names, are bypassing the NetBird DNS/wildcard routing logic. I've tested this on Linux, Windows, and Android clients. In Cloudflare, I've configured: - `vpn.mydomain.com` -> WAN IP In AdGuard I've configured: - `vpn.mydomain.com` -> `192.168.50.16` In NetBird, I've configured the following: - Nameserver for `192.168.50.16` - Configured for all domains - Configured for all peers - Network for MyNetwork - Resources for `192.168.50.16/32`, `192.168.50.0/24`, `*.mydomain.com` - Routed through `gp-srv@192.168.50.24` - Configured for all peers - Policy to allow all peers to `192.168.50.16:53` - Enabled the DNS wildcard routing setting As I mentioned, the expected behavior is that once clients connect to NetBird, they use the configured Nameserver to resolve all DNS queries (`vpn.mydomain.com`, `newegg.com`, `google.com` all go through AdGuard in my case). The actual behavior is that after connecting to NetBird: - `dig`/`nslookup` commands using default servers on clients appear use the NetBird local resolver (`127.0.0.53` for Linux, `100.99.255.254` for Windows). - Unless specifying the AdGuard instance in those `dig`/`nslookup` commands, `vpn.mydomain.com` always resolves to my WAN IP from the Cloudflare DNS record. When specifying the AdGuard instance in those commands, the correct IP (192.168.50.16) is resolved. - When running `tcpdump -ni wt0 udp port 53` on the exit node, only requests for LAN DNS rewrites make it across the exit node, no other DNS requests come through the exit node. **Are you using NetBird Cloud?** Self-hosted NetBird. **NetBird version** `0.60.2` **Is any other VPN software installed?** No **Debug output** To help us resolve the problem, please attach the following anonymized status output `netbird debug for 1m -AS` Attached in a .zip [netbird.debug.454865632.zip](https://github.com/user-attachments/files/23777812/netbird.debug.454865632.zip) **Additional context** I'm willing to be told I did something wrong in setting up NetBird or I'm doing something really dumb on my DNS side of things. Am I incorrect in thinking clients will adjust their DNS settings to take on nameserver configurations from the NetBird tunnel (yes, I did make sure that private DNS settings were turned off on client devices)? **Have you tried these troubleshooting steps?** - [x] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [x] Checked for newer NetBird versions - [~] Searched for similar issues on GitHub (including closed ones) - [x] Restarted the NetBird client - [x] Disabled other VPN software - [x] Checked firewall settings

saavagebueno added the triage-needed label 2026-08-05 01:24:09 -04:00

saavagebueno commented

2026-08-05 01:24:10 -04:00

@TimTheOverlord commented on GitHub (Nov 28, 2025):

As an update, I've done some additional debugging on my client devices:

I am mistaken in saying that other domains (google.com, newegg.com, other LAN names like my IdP at auth.mydomain.com) are not making their way up to the AdGuard Home instance. I've checked on clients and on the exit node again with tcpdump and saw queries exiting clients and receiving responses on wt0. I also did see logs in AdGuard showing resolution of those names.
Queries for vpn.mydomain.com are still routed to, and answered by, the client's lo interface. I've checked, and that name is never resolved with wt0.
The whole system (data plane containers, exit nodes, and clients) has been updated to 0.60.3 with no change in behavior.
I've reconfigured Netbird, with no changes in this problem:
- I've kept the network and it's resources.
- I've added a new group that consists of all peers.
- Via the Networks screen, I've added this group to all of the network resources.
- Via the Groups screen, I've added my Nameserver by IP.
- Via the Groups screen, I've added two network routes: 192.168.50.0/24 and *.mydomain.com both through the gp-srv exit node.
- Via the Groups screen, I've added a policy that permits this group to talk to this group just so it's explicitly indicated.

@TimTheOverlord commented on GitHub (Nov 28, 2025): As an update, I've done some additional debugging on my client devices: - I am mistaken in saying that other domains (google.com, newegg.com, other LAN names like my IdP at auth.mydomain.com) are not making their way up to the AdGuard Home instance. I've checked on clients and on the exit node again with `tcpdump` and saw queries exiting clients and receiving responses on `wt0`. I also did see logs in AdGuard showing resolution of those names. - Queries for vpn.mydomain.com are still routed to, and answered by, the client's `lo` interface. I've checked, and that name is never resolved with `wt0`. - The whole system (data plane containers, exit nodes, and clients) has been updated to `0.60.3` with no change in behavior. - I've reconfigured Netbird, with no changes in this problem: - I've kept the network and it's resources. - I've added a new group that consists of all peers. - Via the Networks screen, I've added this group to all of the network resources. - Via the Groups screen, I've added my Nameserver by IP. - Via the Groups screen, I've added two network routes: `192.168.50.0/24` and `*.mydomain.com` both through the gp-srv exit node. - Via the Groups screen, I've added a policy that permits this group to talk to this group just so it's explicitly indicated.

saavagebueno commented

2026-08-05 01:24:10 -04:00

@TimTheOverlord commented on GitHub (Nov 28, 2025):

I did further experimentation with some kind of success but also not really? I have a Ubiquiti Router (UDM-SE) and have 192.168.50.0/24 as a separate network and had the Isolate Network setting enabled. For whatever reason, this prevented hairpin NATing from redirecting requests from LAN to my WAN back into my LAN. Disabling that setting allows my VPN clients to load vpn.mydomain.com now, but still from the WAN/public name. This happening even though I still have a private DNS name set for vpn.mydomain.com in AdGuard to point to the LAN IP, not public IP. As a note, I've been using a mixture of dig/nslookup and resolvectl query commands with roughly equal performance out of each of them.

So even though I've fixed the hairpin NAT issue, this hasn't changed the DNS issue I've found.

On a Linux client connected to my NetBird instance, running resolvectl status results this:

Global
       Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
      DNS Domain: localdomain netbird.mydomain

Link 2 (enp39s0)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
       DNS Servers: 192.168.1.1
        DNS Domain: localdomain

...

Link 11 (wt0)
    Current Scopes: DNS
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 100.99.234.199
       DNS Servers: 100.99.234.199
        DNS Domain: netbird.mydomain ~. ~99.100.in-addr.arpa

Running resolvectl query portainer.ui.mydomain.com returns the expected AdGuard rewrite:

portainer.ui.mydomain.com: 192.168.50.16   -- link: wt0

-- Information acquired via protocol DNS in 45.6ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: no
-- Data from: network

Meanwhile, running resolvectl query vpn.mydomain.com returns my WAN IP, coming from my Cloudflare DNS entry:

resolvectl query vpn.huffconnect.net
vpn.mydomain.com: [REDACTED WAN IP]             -- link: wt0

-- Information acquired via protocol DNS in 47.3ms.
-- Data is authenticated: no; Data was acquired via local or encrypted transport: no
-- Data from: cache network

And running dig kinda shows the issue pretty transparently:

dig @192.168.50.16 vpn.mydomain.com

; <<>> DiG 9.18.39-0ubuntu0.22.04.2-Ubuntu <<>> @192.168.50.16 vpn.mydomain.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2042
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;vpn.mydomain.com.		IN	A

;; ANSWER SECTION:
vpn.mydomain.com.	10	IN	A	192.168.50.16

;; Query time: 44 msec
;; SERVER: 192.168.50.16#53(192.168.50.16) (UDP)
;; WHEN: Fri Nov 28 19:07:07 EST 2025
;; MSG SIZE  rcvd: 53


dig @100.99.234.199 vpn.mydomain.com

; <<>> DiG 9.18.39-0ubuntu0.22.04.2-Ubuntu <<>> @100.99.234.199 vpn.mydomain.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61894
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;vpn.mydomain.com.		IN	A

;; ANSWER SECTION:
vpn.mydomain.com.	300	IN	A	[REDACTED WAN IP]

;; Query time: 0 msec
;; SERVER: 100.99.234.199#53(100.99.234.199) (UDP)
;; WHEN: Fri Nov 28 19:07:19 EST 2025
;; MSG SIZE  rcvd: 72

In the NetBird Dashboard, I've tried two different configurations with no change. I've tried a simple "Nameserver + Exit Node + Network Route" model with gp-srv@192.168.50.24 as the exit node, a globally set nameserver of 192.168.50.16, and a network route to get to the nameserver via the Exit Node, which was not successful. I've also tried a Network with resources, a Nameserver, DNS wildcard routing, and a routing peer (again being gp-srv@192.168.50.24) with no change either. So I'm not sure what else to try at this point.

@TimTheOverlord commented on GitHub (Nov 28, 2025): I did further experimentation with some kind of success but also not really? I have a Ubiquiti Router (UDM-SE) and have 192.168.50.0/24 as a separate network and had the `Isolate Network` setting enabled. For whatever reason, this prevented hairpin NATing from redirecting requests from LAN to my WAN back into my LAN. Disabling that setting allows my VPN clients to load vpn.mydomain.com now, but still from the WAN/public name. This happening even though I still have a private DNS name set for vpn.mydomain.com in AdGuard to point to the LAN IP, not public IP. As a note, I've been using a mixture of `dig`/`nslookup` and `resolvectl query` commands with roughly equal performance out of each of them. So even though I've fixed the hairpin NAT issue, this hasn't changed the DNS issue I've found. On a Linux client connected to my NetBird instance, running `resolvectl status` results this: ``` Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign DNS Domain: localdomain netbird.mydomain Link 2 (enp39s0) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 192.168.1.1 DNS Servers: 192.168.1.1 DNS Domain: localdomain ... Link 11 (wt0) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 100.99.234.199 DNS Servers: 100.99.234.199 DNS Domain: netbird.mydomain ~. ~99.100.in-addr.arpa ``` Running `resolvectl query portainer.ui.mydomain.com` returns the expected AdGuard rewrite: ``` portainer.ui.mydomain.com: 192.168.50.16 -- link: wt0 -- Information acquired via protocol DNS in 45.6ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: network ``` Meanwhile, running `resolvectl query vpn.mydomain.com` returns my WAN IP, coming from my Cloudflare DNS entry: ``` resolvectl query vpn.huffconnect.net vpn.mydomain.com: [REDACTED WAN IP] -- link: wt0 -- Information acquired via protocol DNS in 47.3ms. -- Data is authenticated: no; Data was acquired via local or encrypted transport: no -- Data from: cache network ``` And running `dig` kinda shows the issue pretty transparently: ``` dig @192.168.50.16 vpn.mydomain.com ; <<>> DiG 9.18.39-0ubuntu0.22.04.2-Ubuntu <<>> @192.168.50.16 vpn.mydomain.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2042 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;vpn.mydomain.com. IN A ;; ANSWER SECTION: vpn.mydomain.com. 10 IN A 192.168.50.16 ;; Query time: 44 msec ;; SERVER: 192.168.50.16#53(192.168.50.16) (UDP) ;; WHEN: Fri Nov 28 19:07:07 EST 2025 ;; MSG SIZE rcvd: 53 dig @100.99.234.199 vpn.mydomain.com ; <<>> DiG 9.18.39-0ubuntu0.22.04.2-Ubuntu <<>> @100.99.234.199 vpn.mydomain.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61894 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;vpn.mydomain.com. IN A ;; ANSWER SECTION: vpn.mydomain.com. 300 IN A [REDACTED WAN IP] ;; Query time: 0 msec ;; SERVER: 100.99.234.199#53(100.99.234.199) (UDP) ;; WHEN: Fri Nov 28 19:07:19 EST 2025 ;; MSG SIZE rcvd: 72 ``` In the NetBird Dashboard, I've tried two different configurations with no change. I've tried a simple "Nameserver + Exit Node + Network Route" model with gp-srv@192.168.50.24 as the exit node, a globally set nameserver of 192.168.50.16, and a network route to get to the nameserver via the Exit Node, which was not successful. I've also tried a Network with resources, a Nameserver, DNS wildcard routing, and a routing peer (again being gp-srv@192.168.50.24) with no change either. So I'm not sure what else to try at this point.

Sign in to join this conversation.

Branches Tags

main

claude/agent-network-test-cases-p743vw

android/gui-integration

revert/component-types

feat-post_quantum_ml_kem

ice-stun-wg-demux

dependabot/npm_and_yarn/proxy/web/npm_and_yarn-b39864987c

agent-network-setup-poc

dependabot/go_modules/aws-sdk-8f849ebaed

dependabot/github_actions/actions-a940c7c866

dependabot/go_modules/otel-e34c790afd

dependabot/go_modules/testcontainers-de325c0dd6

dependabot/go_modules/wireguard-dbd6b95108

dependabot/go_modules/pion-5f703e1eca

dependabot/go_modules/gorm-2271c8195b

fix-login-needed-check

dependabot/go_modules/google.golang.org/grpc-1.82.1

fix/ui-gtk3-support

enterprise-traefik-and-migration-fixes

disambiguate_p2p_metrics

revert/component-types-hookup

embedded-vnc

feature/ios-ssh

docs/agent-network-docs-update

dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/s3-1.106.3

dependabot/go_modules/github.com/pion/stun/v3-3.1.5

fix-ssh-authorized-users-multi-rule

peer-acl-multi-source

reverse-proxy-crowdsec-appsec

reverse-proxy-allow-match-or

client-local-metrics

lazy-conn-per-peer

lazy-conn-rosenpass

dependabot/go_modules/github.com/gopacket/gopacket-1.7.0

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.6

dependabot/go_modules/github.com/pires/go-proxyproto-0.15.0

dependabot/go_modules/github.com/jackc/pgx/v5-5.10.0

dependabot/go_modules/github.com/oapi-codegen/runtime-1.6.0

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.4

dependabot/go_modules/github.com/pkg/sftp-1.13.11

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.20.0

ssh-windows-privilege-check

fix/explicit-cors-handling

fix/remove-math-rand

test/gui-memory-leak-fix

fix/ui-status-dispatch

install-script-ui-dependencies

fix/grpc-get-network-map

fix/subscribe-status-coalesce

fix/tray-menu-item-leak

fix/windows-tray-race

feature/changeset

worktree-dns-route-qtype-fallthrough

mdm_integration

mlsmaycon-patch-2

feat/agent-network-ollama

proxy-tunnel-cache-ttl-env

coderabbitai/utg/1e5b0a5

grpc-acl

test/battery-drain

components-impl-drop-indexes-use-xids-no-resource-policy-map

fix/nmap-relevant-groups

e2e-guardrail-blocks-unselected-model

fix/lazyconn-cold-start-allowed-ips

vertex-guardrails-model-access-e2e

add-atomic-cache-ops

refactor/relay-foreign-cache

ci/trigger-release-tests

feature/kimi-3-agent-networks-dns-warmup

feature/dns-lazy-conn-warmup

daemon-ipc-acl

feature/ui-translation-key-parity-check

refactor/relay-foreign-cache-tests

fix/lazyconn-idle-keep-wg-peer

dmitri-propagate-auth-grant-types-on-combined

0.74.7-branch

diagnose-empty-vs-corrupt-state

windows-sleep-detector

fix/cli-up-wait-for-daemon

rp_key_persistency

feature/native-grpc

0.74.6-branch

0.74.6-branch-sync

0.74.5-branch-sync

0.74.4-branch

fix/remove-stale-peers-removal

fix/remove-stale-proxy-logic

fix/nsis-preserve-autostart-on-upgrade

refactor/peer-event-bus

dependabot/go_modules/goauthentik.io/api/v3-3.2026050.3

dependabot/go_modules/github.com/pkg/sftp-1.13.10

components-impl-drop-indexes

fix-reset-aggregation-window-flake

dependabot/go_modules/github.com/pion/dtls/v3-3.1.5

0.74.x

fix/relay-states-lock

update-process-pkg

update-gopsutil-v4

fix/relay_states_lock

increase-sysinfo-timeout

dependabot/go_modules/github.com/Azure/go-ntlmssp-0.1.1

dependabot/go_modules/github.com/eko/gocache/store/redis/v4-4.2.6

dependabot/go_modules/github.com/eko/gocache/lib/v4-4.2.3

fix/fail-to-create-upnp-port-mapping-on-opnsense-firewall

0.74.3-branch

fix/routeselector-atomic-exit-node

netmap_progressive_alignment

nmap/components-impl

dependabot/go_modules/github.com/jackc/pgx/v5-5.9.2

dependabot/go_modules/github.com/oapi-codegen/runtime-1.4.2

dependabot/go_modules/github.com/gopacket/gopacket-1.6.1

dependabot/go_modules/github.com/coreos/go-oidc/v3-3.19.0

dependabot/go_modules/github.com/pires/go-proxyproto-0.12.0

fix/signal-watchdog-sync-stop

docs/agent-network

test/affected-logic

fix/revert-ice-filter

refactor/simplify-affected-peers

pascal-filter-policies-by-direction

claude/lock-contention-peer-connect-g8t6au

dmitri-filter-policies-by-direction

refactor/migrate-profiles-to-go

profile-bindings-ios

fix/skip-restart-unchanged-route

fix/mgmt-cache-async-resolve

refactor/wails-update-105

client_lifetime_serialization_refactor

fix/browser-ssh-2

fix/ipv6-and-netstack-accept-loop

fix/browser-ssh

profile-id-name-test

refactor/mgmt-bootstrap

feat/getting-started-unified-wizard

socket-grpc-permissions

fix/mysql-index-migration

windows-dns-firewall

tests/enable-race-on-tests

ui-refactor-gtk3

feature/affected-peers-grpc

profile-id

lazyconn-first-packet-fix-v2

claude/focused-gates-VMTgb

ui-tray-linux-leftclick

fix/ctx-enrichment

daemon-owner

feature/android-client-ssh

worktree-accept-ra-forwarding

nmap/combined-deploy

task/align_protobuff_toolset

feature/session-extend

add-json-yaml-flags

refactor/ephemeral-cleanup

claude/webtransport-relay-wasm-mUjY9

claude/vnc-udp-feasibility-6KB1U

fix/wgport-config

e2e-windows-dns-combined

fix/login-cmd-root-flags

feat/reseller-openapi-spec

github-issue-resolver

add-steamos-support

fix-darwin-uninstaller

flutter-test

ci/freebsd-pkg-bootstrap

cached-serial-check-on-sync

fix-mgmt-cache-bypass-overlay

revert-easyjson-5938

revert-ice-5820

revert-firewalld-5928

refactor/permissions-manager

revert-dns-5935-systemd-resolved

revert-dns-5935-5945

revert-dns-5945-mgmt-cache

feature/log-most-busy-peers

prototype/ui-wails

coderabbitai/utg/8ae8f20

feature/use-peer-fqdn-on-https

release/0.68.3

add-slack-channel

claude/rdp-token-passthrough-eNcqW

transparent-proxy

fix/macos-stale-route-eexist

crowdsec-selfhosted

fix/remove-otel-units

entire/checkpoints/v1

fix/getting-started

feat/static-connectors-combined-server

feature/use-local-keys-embedded

feature/fleetdm

set-env-only-if-not-fork

feature/expose-has-channel

fix/connection-status-race

fix/filter-cgnat-cni-ice-candidates

feature/check-cert-locker-before-acme

test/proxy-fixes

test/proxy-mtu

prototype/ui-tauri

test/proxy-speed

fix-reused-ports

feat/migrate-to-embedded-idp

feature/add-serial-to-proxy-merged

deploy/proxy-serial

test/connection

feature/disable-legacy-port

feature/flag-to-disable-legacy-port

test/perftest

fix/http-redirect

poc-token-command

dn-reverse-proxy

prototype/reverse-proxy-rename

prototype/reverse-proxy-logs-pagination

feature/client-metrics

prototype/reverse-proxy-clusters

debug-dns-route

fix/win-dns-batch

add-extra-route-logs

job-stream-notify-disconnection-eof

deploy/secrets-manager

trigger-proxy-update

bug/update-ios-client-code-build-tags

sync-client-netmap-serial

log/conn-disconn

nmap/compaction-deploy

ci-win-test

feature/disk-encryption-check

wasm-debug

swap-dns-prio

fix/dex-config

feature/migrate-auto-groups-to-table

nmap/compaction

dex-nocgo-stub

feature/exclude-terraform-from-rate-limiting

test-freebsd

retries-refactor

coderabbitai/docstrings/b7e98ac

feat/integrate-zitadel

bug/ios-hanging-reconection

zitadel-idp

feat/network-map-serial

refactor/get-account-no-users

feat/auto-upgrade

feature/report-high-pat-id

feature/temporary-access-for-resource

fix/nmap-fwrules

dont-restart-dns

prototype/ui

update-gomobile

go-dns-for-ice

wasm-ldflags

test-ldflags

wasmbuild-test

feature/networks-s2s

vk/compare-nmaps

dbg/bothmaps

reorder-dns-shutdown

fix/relay-reconnection-race

fix/nmap-exitnodes

vk/debug/nmap-both

move-licensed-code

feat/better-daemon-connection-lost-message

feat/auto-update-2

test/timings

refactor/getaccount-raw

tests/nmap-getaccount

refactor/nmap

refactor/nmap-limit-buffer

feature/detect-mac-wakeup

feature/extract-modules

quick-setings

feat/sync-limiter

feature/store-cache-impl

fix-install-version

feature/store-metrics

feature/metrics-on-store

feature/use-gorm-cache

loadtest-signal

unsymmetrical-squash

refactor/reducate-signaling

test/update-reduce

feature/store-cache

feature/remote-debug

cli-ws-proxy-backend-addr

feat/mgmt-map-serial

snyk-fix-d9d0081a4c7f9137bdb59d0d50a141a2

snyk-fix-7415cea5a11acd66753540ca2c598c63

job-yml-update

feature/android-allow-selecting-routes

fix/up-sequence

fix/dns-hash-update

snyk-fix-967adae9863f17f108ce8948d9117b8d

log/getaccount-by-peer

signal-suppressor

dns-exit-node

feature/auto-updates

feature/cache-srv-key

merged-fixes

fix/missed-offers-and-debug

debug-and-fixes

poc-wasm-clean-backend-s2s

test/remote-debug

debug-api

fix/remove-gpo-if-empty

fix/test-freebsd

fix/mysql-setup

fix/remove-logout-btn

handle-existing-domain-user

chore/unify-domain-validation

snyk-fix-c5fafc8a50ce1f29046e25a1fc346185

feat/profile-edit-btn

snyk-fix-a54966211e18d4cf67e5a2757cc006d1

log-short-id

feat/logout-ephemeral

log-checks

batch-wg-ops

nb-interface-default

feat/aws-integration

add/race-test

feature/relay-feature-versioning

fix/systemd-service-logs

poc/preprocessed-map

add-account-onboarding

bind-ipv6

fix/merge-main

logs/peerlogs-addpeer

feature/net-297-network-migration

feature/support-skip-auto-apply-exit-node-routes

set-cmd

set-command-with-cursor

feature/limit-update-channel

stop-using-locking-share

feature/poc-lazy-detection

feature/net-248-removal-of-sync-mutex-locks

test/multiple-peer-logging

preresolve

add-ns-punnycode-support

apply-routes-early

windows-search-domains

fix/connecting-route-filter

feature/management/rest-client/impersonate

debug-local-records

resource-fields-snake-case

test/grpc-rate-limit

traffic-correlation-policy

feature/rest-client-options

feat/events-metrics

feature/buf-cli

test/add-ratelimiter

test/remove-write-lock-on-add-peer

fix/add-peer-semaphore

feature/users-roles-endpoint

mlsmaycon-patch-1

debug-user-role

chore/primary-key-on-networks

feature/update-account-peers-buffer-startup

remove-ubuntu2004-runners

refactor/permissions-no-pat-allowed

ref/logrus-factory

use-conntrack-zone

deploy/permissions-account

feature/lazy-connection-idle

ref/improve-test-cov

restore-pr-3440

test/increase-grpc-timeouts

feat/buffer-account-peers-update

test/networkmapgeneration-changes

feature/base-manager

feature/flow-receiver

chore/benchmark-with-large-runner

refactor/handshake-initiator

client/ui-update-systray-icons

userspace-router

wgwatcher-test

output-if-key-already-exists

fix/relay-reconnection

feature/port-forwarding-client-codecleaning

detached2

test/callbacks-nil-iceconninfo

refactor/optimize-peer-expiration

enable-udp-port-for-docker-template

fix/relay-update

feature/apply-posture-netmap

fix/group-update-existing-resource

conntrack-stats

upgrade-okta-sdk

multi-price

test/conn-stat

set-min-parallel-tests-for-management

dns-interceptor

debug-dns

router-dns

add-static-system-info

debug-0.29.4

debug-0.33.0

account-refactoring

relay/2800_quic

route-get-account-refactoring

test/seed-random-routes

feature/get-account-refactoring

test/reconnect-race-condition

refactor/get-account-usage

feature/add-session-id-to-update-channel

improve-ipv4conn

fix/async-pion-event-handling

debug

add-offload

feature/validate-group-association-debug

fix/limit-conn-for-sqlite

test/engine-iface

test/transaction-for-jwt-sync

fix/engine-stop-in-foreground

feature/add-mysql-support

test-migration

refactor/header-size-values

relay/eliminate-gob

test/signal-dispatcher-with-relay

relay/debug

validate-icon

feature/ipv6-support

use-pre-expanded-peers-map

feature/use-signal-dispatcher

validate/peer-status

add-read-write-times

fix/sync-peer-race

feature/relay-status

netmap

evaluate/network-map-hash

fix/lower-dns-resolve-interval-on-fail

feature/relay

fix/go-mod-version

upgrade-nftables

synology-userspace-mode

fix/use-ip-for-default-routes-on-darwin

fix/proxy_close

enable-release-workflow-on-pr

deploy/peer-performance

feature/permanent-turn

feature/permanent-turn-proxy

deploy/posture-check-sqlite

feature/optimize_sqlite_save

debug-ios-behavior

fix/delete-route-only-after-adding

tshoot/windows-logger

remove-new-routing

refactor/eliminate-repo-dependency

add-arm-to-ci

refactor-demo-account-object

test/abc2

test/abc

send-ssh-rosenpass-config-meta

refactor-demo

ensure-schedule-never-runs-non-positive

feature/peer-validator-groupmgm

feature/peer-validator-fix

fix/include-active-dashboard-users

fix/handle-canceling-schedule

fix/geo-download

debug-google-workspace

yury/resolve-ip-to-location

feature/extend-sysinfo

sqlite-async-peer-status

yury/add-postgresql-store

fix/route

test-build

posture-checks-poc

debug-keycloak-idp

poc/netstack

for-pascal-tmp

peer-logout-management

manual-peer-logout

detached

chore/refactor-management

test/dns-bind

fix/enforce-acl-for-containers

yury/use-sync-map-in-updatechannel

fix/events-key-handling

filter-cache-on-load-account

fix/user-expiration

handle-user-context-cancellation

nb-client-k8s-statefulset

fake-addr

fix/iptables_in_docker

ebpf-debug

update-getting-started-flow-use-postgres

fix/peer_list_notification

feature/device-authentication-with-client-secret

feature/keep_alive

feat-groups-from-jwt

separate_proxy_from_wgconfig

fix/wg_conn

wg_conn_fix

wg_bind_parallel_processing

fix-rollback-get-acls

proxy_cfg_cleanup

performance-improvement-rego

update-lock-log-level

feat-client-side-acl

refactor/move_grpcserver_logic_to_account_manager

feature/event-storage

feature/update-idp-redeeming-invite

feature/api-peer-info

return-groupminimum-setupkey

feature/interface-bind

documentation_enhancement

fix-peer-registration

ssh

users_cache

pass-client-caller

client_caller_type

revert-283-feat-fix-windows-installer

periodic-peer-updates

ebpf

braginini/wasm

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: DYNR/netbird#9962