DNS Fallback #247

Closed
opened 2025-11-20 05:08:33 -05:00 by saavagebueno · 3 comments
Owner

Originally created by @cfouche3005 on GitHub (Dec 4, 2022).

Originally assigned to: @mlsmaycon on GitHub.

Describe the problem
I use multiple adguard instances as DNS server but when is one instance is down, certain peer doesn't fallback to the second dns unless I disable it in Netbird.

To Reproduce
Steps to reproduce the behavior:

  1. Create multiple Nameserver in https://app.netbird.io/dns
  2. Down one DNS server
  3. See error

Expected behavior
All peer should fallbak to the other dns server

NetBird status -d output:

 serv-lavos.netbird.cloud:
  NetBird IP: 100.105.92.118
  Public key: ntpT+bg9zh1A+iFCnZyux+HBSEY6ktMXvW14FIuz8nQ=
  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true
  ICE candidate (Local/Remote): host/host
  Last connection update: 2022-12-04 00:05:53

 serv-monitor.netbird.cloud:
  NetBird IP: 100.105.153.66
  Public key: oHo+rgUKfop2+u6CUrep4MuBDcnndqpx1nxy3lBaZBw=
  Status: Connected
  -- detail --
  Connection type: P2P
  Direct: true
  ICE candidate (Local/Remote): host/prflx
  Last connection update: 2022-12-04 11:51:13

Daemon version: 0.11.3
CLI version: 0.11.3
Daemon status: Connected
Management: Connected to https://api.wiretrustee.com:443
Signal:  Connected to https://signal2.wiretrustee.com:443
Domain: serv-lotus.netbird.cloud
NetBird IP: 100.105.210.93/16
Interface type: Kernel
Peers count: 2/2 Connected

Lavos fallback but the other not.

Screenshots
image
Lotus DNS is down and certain peer doesn't fallback to Monitor DNS
image
On Lotus it doesn't work
image
But on Lavos it works

Originally created by @cfouche3005 on GitHub (Dec 4, 2022). Originally assigned to: @mlsmaycon on GitHub. **Describe the problem** I use multiple adguard instances as DNS server but when is one instance is down, certain peer doesn't fallback to the second dns unless I disable it in Netbird. **To Reproduce** Steps to reproduce the behavior: 1. Create multiple Nameserver in https://app.netbird.io/dns 2. Down one DNS server 3. See error **Expected behavior** All peer should fallbak to the other dns server **NetBird status -d output:** ```Peers detail: serv-lavos.netbird.cloud: NetBird IP: 100.105.92.118 Public key: ntpT+bg9zh1A+iFCnZyux+HBSEY6ktMXvW14FIuz8nQ= Status: Connected -- detail -- Connection type: P2P Direct: true ICE candidate (Local/Remote): host/host Last connection update: 2022-12-04 00:05:53 serv-monitor.netbird.cloud: NetBird IP: 100.105.153.66 Public key: oHo+rgUKfop2+u6CUrep4MuBDcnndqpx1nxy3lBaZBw= Status: Connected -- detail -- Connection type: P2P Direct: true ICE candidate (Local/Remote): host/prflx Last connection update: 2022-12-04 11:51:13 Daemon version: 0.11.3 CLI version: 0.11.3 Daemon status: Connected Management: Connected to https://api.wiretrustee.com:443 Signal: Connected to https://signal2.wiretrustee.com:443 Domain: serv-lotus.netbird.cloud NetBird IP: 100.105.210.93/16 Interface type: Kernel Peers count: 2/2 Connected ``` Lavos fallback but the other not. **Screenshots** ![image](https://user-images.githubusercontent.com/51720655/205488404-f4934d93-cec8-494b-839f-9881ba383ab8.png) Lotus DNS is down and certain peer doesn't fallback to Monitor DNS ![image](https://user-images.githubusercontent.com/51720655/205488479-660b2919-384e-41e2-a12b-246d7fbf3aec.png) On Lotus it doesn't work ![image](https://user-images.githubusercontent.com/51720655/205488510-e7e3362f-f39f-4e38-a223-7d2aaf7b9b2c.png) But on Lavos it works
saavagebueno added the bugclient labels 2025-11-20 05:08:33 -05:00
Author
Owner

@cfouche3005 commented on GitHub (Dec 4, 2022):

After more test, DNS doesn't change unless I restart all netbird peers

@cfouche3005 commented on GitHub (Dec 4, 2022): After more test, DNS doesn't change unless I restart all netbird peers
Author
Owner

@mlsmaycon commented on GitHub (Dec 8, 2022):

Thanks for opening this issue @cfouche3005, we need to add an event connection between peers and the DNS configuration.

@mlsmaycon commented on GitHub (Dec 8, 2022): Thanks for opening this issue @cfouche3005, we need to add an event connection between peers and the DNS configuration.
Author
Owner

@mlsmaycon commented on GitHub (Jun 16, 2023):

In #901 We've implemented a retry logic that validates the communication with private upstream services.

@mlsmaycon commented on GitHub (Jun 16, 2023): In #901 We've implemented a retry logic that validates the communication with private upstream services.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#247