[GH-ISSUE #2303] domain routes don't work on client #4583

Open
opened 2026-08-05 00:58:31 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @emperorkebab on GitHub (Jul 22, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2303

Describe the problem

domain routes don't work on my ubuntu and windows clients, i can ping my other docker peer either by its netbird ip or name, i can even ping a local machine (in the peer's network) by using an ip route, but domain routes don't work

I verified that the domain is resolvable and accessible inside my peer's docker container, and that the container has the 3 needed cap_adds
The domain route is correctly setup, with the docker peer as routing peer, and the distribution group assigned to the clients

i even tried hosting a webserver with the route's domain name inside the docker peer, with no avail
The only workaround is to create an ip route and manually add the domain mapping in the client hosts file, which is unpractical
Potentially related to https://github.com/netbirdio/netbird/issues/1788


To Reproduce

Steps to reproduce the behavior:

  1. I created a domain route with the docker peer as routing peer, and the distribution group of the client
  2. use netbird up (with debug flags)

Expected behavior

The client should ping and connect to the domain of the domain route successfully


NetBird version

0.28.4 for:

  • Self hosted management
  • docker peer
  • ubuntu client
  • windows client

Outputs

netbird up debug log (ubuntu client):

024-07-22T19:26:52+02:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 1.138681ms, total rules count: 2
2024-07-22T19:26:53+02:00 ERRO client/internal/routemanager/dynamic/route.go:165: Failed to resolve domains for route [mydomain.com]: resolve domains: 1 errors occurred:
	* resolve d mydomain.com: lookup mydomain.com on 127.0.0.53:53: no such host
2024-07-22T19:26:53+02:00 ERRO client/internal/routemanager/dynamic/route.go:165: Failed to resolve domains for route [mydomain.com]: resolve domains: 1 errors occurred:
	* resolve d mydomain.com: lookup mydomain.com on 127.0.0.53:53: no such host
2024-07-22T19:26:53+02:00 ERRO client/internal/routemanager/dynamic/route.go:165: Failed to resolve domains for route [mydomain.com]: resolve domains: 1 errors occurred:
	* resolve d mydomain.com: lookup mydomain.com on 127.0.0.53:53: no such host

client ping error (ubuntu client):

ping: mydomain.com: Temporary failure in name resolution

netbird status (ubuntu client):

Peers detail:
 mydockerpeer.netbird.selfhosted:
  NetBird IP: 100.101.142.98
  Public key: *removed*
  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true
  ICE candidate (Local/Remote): host/srflx
  ICE candidate endpoints (Local/Remote): 192.168.82.102:51820/198.74.80.1:51820
  Last connection update: 22 seconds ago
  Last WireGuard handshake: 10 seconds ago
  Transfer status (received/sent) 420 B/660 B
  Quantum resistance: false
  Routes: -
  Latency: 61.711842ms

OS: linux/amd64
Daemon version: 0.28.4
CLI version: 0.28.4
Management: Connected to https://anon-HPxz3.domain:8080
Signal: Connected to https://anon-HPxz3.domain:8080
Relays: 
  [stun:anon-HPxz3.domain:3478] is Available
  [turn:anon-HPxz3.domain:3478?transport=udp] is Available
Nameservers: 
FQDN: myclient.netbird.selfhosted
NetBird IP: 100.95.37.12/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected
Originally created by @emperorkebab on GitHub (Jul 22, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2303 **Describe the problem** domain routes don't work on my ubuntu and windows clients, i can ping my other docker peer either by its netbird ip or name, i can even ping a local machine (in the peer's network) by using an ip route, but domain routes don't work I verified that the domain is resolvable and accessible inside my peer's docker container, and that the container has the 3 needed cap_adds The domain route is correctly setup, with the docker peer as routing peer, and the distribution group assigned to the clients i even tried hosting a webserver with the route's domain name inside the docker peer, with no avail The only workaround is to create an ip route and manually add the domain mapping in the client hosts file, which is unpractical Potentially related to https://github.com/netbirdio/netbird/issues/1788 --- **To Reproduce** Steps to reproduce the behavior: 1. I created a domain route with the docker peer as routing peer, and the distribution group of the client 2. use netbird up (with debug flags) --- **Expected behavior** The client should ping and connect to the domain of the domain route successfully --- **NetBird version** 0.28.4 for: - Self hosted management - docker peer - ubuntu client - windows client --- **Outputs** netbird up debug log (ubuntu client): ``` 024-07-22T19:26:52+02:00 INFO client/internal/acl/manager.go:52: ACL rules processed in: 1.138681ms, total rules count: 2 2024-07-22T19:26:53+02:00 ERRO client/internal/routemanager/dynamic/route.go:165: Failed to resolve domains for route [mydomain.com]: resolve domains: 1 errors occurred: * resolve d mydomain.com: lookup mydomain.com on 127.0.0.53:53: no such host 2024-07-22T19:26:53+02:00 ERRO client/internal/routemanager/dynamic/route.go:165: Failed to resolve domains for route [mydomain.com]: resolve domains: 1 errors occurred: * resolve d mydomain.com: lookup mydomain.com on 127.0.0.53:53: no such host 2024-07-22T19:26:53+02:00 ERRO client/internal/routemanager/dynamic/route.go:165: Failed to resolve domains for route [mydomain.com]: resolve domains: 1 errors occurred: * resolve d mydomain.com: lookup mydomain.com on 127.0.0.53:53: no such host ``` client ping error (ubuntu client): ``` ping: mydomain.com: Temporary failure in name resolution ``` netbird status (ubuntu client): ``` Peers detail: mydockerpeer.netbird.selfhosted: NetBird IP: 100.101.142.98 Public key: *removed* Status: Connected -- detail -- Connection type: P2P Direct: true ICE candidate (Local/Remote): host/srflx ICE candidate endpoints (Local/Remote): 192.168.82.102:51820/198.74.80.1:51820 Last connection update: 22 seconds ago Last WireGuard handshake: 10 seconds ago Transfer status (received/sent) 420 B/660 B Quantum resistance: false Routes: - Latency: 61.711842ms OS: linux/amd64 Daemon version: 0.28.4 CLI version: 0.28.4 Management: Connected to https://anon-HPxz3.domain:8080 Signal: Connected to https://anon-HPxz3.domain:8080 Relays: [stun:anon-HPxz3.domain:3478] is Available [turn:anon-HPxz3.domain:3478?transport=udp] is Available Nameservers: FQDN: myclient.netbird.selfhosted NetBird IP: 100.95.37.12/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 1/1 Connected ```
saavagebueno added the clientdnsdocker labels 2026-08-05 00:58:31 -04:00
Sign in to join this conversation.
No Label client dns docker
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4583