[GH-ISSUE #2239] DNS Resolution Debian 11 and 12 not working as expected - Name or Service not known #4470

Open
opened 2026-08-05 00:57:52 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @VanLampe on GitHub (Jul 5, 2024).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/2239

Hi together,

I am currently trying the selfhosted installation of netbird. So far everything is working properly, but I have some issues with the dns resolution.

It seems, that the dns resolver is not resolving the fqdn of connected peers under debian VMs.

I have some peers added to the netbird mesh but I am not able to reach a peer by its fqdn from the linux / debian hosts. On Android and Windows, I can call the peers via fqdn.

ping app.netbird.selfhosted
ping: app.netbird.selfhosted: Name or service not known

ssh app.netbird.selfhosted
ssh: Could not resolve hostname app.netbird.selfhosted: Name or service not known

Connecting via the overlay IP is working without issues:

ping 100.69.131.193
PING 100.69.131.193 (100.69.131.193) 56(84) bytes of data.
64 bytes from 100.69.131.193: icmp_seq=1 ttl=64 time=0.351 ms
64 bytes from 100.69.131.193: icmp_seq=2 ttl=64 time=0.262 ms
^C
--- 100.69.131.193 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1029ms

Also using dig, the fqdn seems to resolve correctly:

dig app.netbird.selfhosted

; <<>> DiG 9.18.24-1-Debian <<>> app.netbird.selfhosted
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4865
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;app.netbird.selfhosted.                IN      A

;; ANSWER SECTION:
app.netbird.selfhosted. 300     IN      A       100.69.131.193

;; Query time: 3 msec
;; SERVER: 100.69.179.157#53(100.69.179.157) (UDP)
;; WHEN: Fri Jul 05 12:00:49 UTC 2024
;; MSG SIZE  rcvd: 78

/etc/resolv.conf

# Generated by NetBird
# If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird

options timeout:4 attempts:1
search netbird.selfhosted local
nameserver 100.69.179.157
nameserver <ip of my local dns server>
nameserver 8.8.8.8

I recognized, that the resolv.conf only gets updated, if I reconnect the netbird agent after rebooting the VM (netbird down and up). I think this is caused by the proxmox hypervisor, that is applying the global dns settings for my proxmox hosts.

Can anyone help me to solve this issue?

Thanks and best regards,
Frank

Originally created by @VanLampe on GitHub (Jul 5, 2024). Original GitHub issue: https://github.com/netbirdio/netbird/issues/2239 Hi together, I am currently trying the selfhosted installation of netbird. So far everything is working properly, but I have some issues with the dns resolution. It seems, that the dns resolver is not resolving the fqdn of connected peers under debian VMs. I have some peers added to the netbird mesh but I am not able to reach a peer by its fqdn from the linux / debian hosts. On Android and Windows, I can call the peers via fqdn. ``` ping app.netbird.selfhosted ping: app.netbird.selfhosted: Name or service not known ssh app.netbird.selfhosted ssh: Could not resolve hostname app.netbird.selfhosted: Name or service not known ``` Connecting via the overlay IP is working without issues: ``` ping 100.69.131.193 PING 100.69.131.193 (100.69.131.193) 56(84) bytes of data. 64 bytes from 100.69.131.193: icmp_seq=1 ttl=64 time=0.351 ms 64 bytes from 100.69.131.193: icmp_seq=2 ttl=64 time=0.262 ms ^C --- 100.69.131.193 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1029ms ``` Also using `dig`, the fqdn seems to resolve correctly: ``` dig app.netbird.selfhosted ; <<>> DiG 9.18.24-1-Debian <<>> app.netbird.selfhosted ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4865 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;app.netbird.selfhosted. IN A ;; ANSWER SECTION: app.netbird.selfhosted. 300 IN A 100.69.131.193 ;; Query time: 3 msec ;; SERVER: 100.69.179.157#53(100.69.179.157) (UDP) ;; WHEN: Fri Jul 05 12:00:49 UTC 2024 ;; MSG SIZE rcvd: 78 ``` `/etc/resolv.conf` ``` # Generated by NetBird # If needed you can restore the original file by copying back /etc/resolv.conf.original.netbird options timeout:4 attempts:1 search netbird.selfhosted local nameserver 100.69.179.157 nameserver <ip of my local dns server> nameserver 8.8.8.8 ``` I recognized, that the `resolv.conf` only gets updated, if I reconnect the netbird agent after rebooting the VM (netbird down and up). I think this is caused by the proxmox hypervisor, that is applying the global dns settings for my proxmox hosts. Can anyone help me to solve this issue? Thanks and best regards, Frank
saavagebueno added the dns label 2026-08-05 00:57:52 -04:00
Sign in to join this conversation.
No Label dns
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#4470