[GH-ISSUE #2069] DNS Name Resolution of internal hostnames works only a few hours #3973

Open
opened 2026-08-05 00:55:16 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @jogrie on GitHub (May 28, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2069

Describe the problem

Hi there,

i want to use Netbird to connect my homelab to my cloud server.

I am using internal Domain Names and have problems to resolve these names.

the setup looks like this

cloud server -> netbird connection -> home server -> netbird route -> dns server

on the home server i have ntfy.sh running so i can send me notifications when e.g. a backup is done.

my acl look like this

cloud server <-> home server - allow ping
cloud server -> home server - allow http / https

my network routes look like this

name: dns
dst: 192.168.178.105/32
router: home server

name: reverse proxy
dst 192.168.178.100/32 (home server ip)
router: home server

my dns config for the cloud server
192.168.178.105
All Domains

Both servers are debian 12 servers
at the moment the connection is only used once at night to send a notification for a finished backup

when connecting the cloud to the home server dns resolution works fine
i can ping the home server with the domain name ntfy.home.example.com

curl -d "Test" ntfy.home.example.com/test
works fine

now the problem

after a few hours / days the dns resolution is not working anymore

if i ping the ip 192.168.178.100 it works fine
if i ping the hostname - unknown hostname

seems like the dns resolution is gone

in the netbird status -d it says Nameserver available (see below)

To Reproduce

Steps to reproduce the behavior:

see above

Expected behavior

I expectet that the dns resolution is working not only a few hours

Are you using NetBird Cloud?

Yes

NetBird version

0.27.3 on both sides

NetBird status -d output:

netbird status -d
Peers detail:
 homeserver.netbird.cloud:
  NetBird IP: 100.74.168.78
  Public key: 9d/Y7q0AmiJ70OdL7CRGuiP5NkOk3SFOevkDTHqdjyY=
  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true
  ICE candidate (Local/Remote): host/prflx
  ICE candidate endpoints (Local/Remote): XXX.XXX.XXX.XXX:51820/XXX.XXX.XXX.XXX:51820
  Last connection update: 2024-05-26 21:26:03
  Last WireGuard handshake: 2024-05-28 21:12:06
  Transfer status (received/sent) 366.8 KiB/247.9 KiB
  Quantum resistance: false
  Routes: 192.168.178.100/32, 192.168.178.105/32
  Latency: 11.045915ms

Daemon version: 0.27.3
CLI version: 0.27.3
Management: Connected to https://api.netbird.io:443
Signal: Connected to https://signal.netbird.io:443
Relays: 
  [stun:stun.netbird.io:5555] is Available
  [turns:turn.netbird.io:443?transport=tcp] is Available
Nameservers: 
  [192.168.178.105:53] for [.] is Available
FQDN: cloudserver.netbird.cloud
NetBird IP: 100.74.138.188/16
Interface type: Kernel
Quantum resistance: false
Routes: -
Peers count: 1/1 Connected
Originally created by @jogrie on GitHub (May 28, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2069 **Describe the problem** Hi there, i want to use Netbird to connect my homelab to my cloud server. I am using internal Domain Names and have problems to resolve these names. the setup looks like this cloud server -> netbird connection -> home server -> netbird route -> dns server on the home server i have ntfy.sh running so i can send me notifications when e.g. a backup is done. my acl look like this cloud server <-> home server - allow ping cloud server -> home server - allow http / https my network routes look like this name: dns dst: 192.168.178.105/32 router: home server name: reverse proxy dst 192.168.178.100/32 (home server ip) router: home server my dns config for the cloud server 192.168.178.105 All Domains Both servers are debian 12 servers at the moment the connection is only used once at night to send a notification for a finished backup when connecting the cloud to the home server dns resolution works fine i can ping the home server with the domain name ntfy.home.example.com curl -d "Test" ntfy.home.example.com/test works fine now the problem after a few hours / days the dns resolution is not working anymore if i ping the ip 192.168.178.100 it works fine if i ping the hostname - unknown hostname seems like the dns resolution is gone in the netbird status -d it says Nameserver available (see below) **To Reproduce** Steps to reproduce the behavior: see above **Expected behavior** I expectet that the dns resolution is working not only a few hours **Are you using NetBird Cloud?** Yes **NetBird version** 0.27.3 on both sides **NetBird status -d output:** ``` netbird status -d Peers detail: homeserver.netbird.cloud: NetBird IP: 100.74.168.78 Public key: 9d/Y7q0AmiJ70OdL7CRGuiP5NkOk3SFOevkDTHqdjyY= Status: Connected -- detail -- Connection type: P2P Direct: true ICE candidate (Local/Remote): host/prflx ICE candidate endpoints (Local/Remote): XXX.XXX.XXX.XXX:51820/XXX.XXX.XXX.XXX:51820 Last connection update: 2024-05-26 21:26:03 Last WireGuard handshake: 2024-05-28 21:12:06 Transfer status (received/sent) 366.8 KiB/247.9 KiB Quantum resistance: false Routes: 192.168.178.100/32, 192.168.178.105/32 Latency: 11.045915ms Daemon version: 0.27.3 CLI version: 0.27.3 Management: Connected to https://api.netbird.io:443 Signal: Connected to https://signal.netbird.io:443 Relays: [stun:stun.netbird.io:5555] is Available [turns:turn.netbird.io:443?transport=tcp] is Available Nameservers: [192.168.178.105:53] for [.] is Available FQDN: cloudserver.netbird.cloud NetBird IP: 100.74.138.188/16 Interface type: Kernel Quantum resistance: false Routes: - Peers count: 1/1 Connected ```
saavagebueno added the bugclientdnscloud labels 2026-08-05 00:55:16 -04:00
Sign in to join this conversation.
No Label bug client cloud dns
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#3973