Custom DNS (hosted by peer) not used by that peer #2190

Open
opened 2025-11-20 07:05:31 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @nmapx on GitHub (Aug 15, 2025).

Describe the problem

Possible bug? Hosting custom DNS server on one of the peers causes this peer not using this DNS server in local resolver. For some reason if peer receives it's own IP address in DNS configuration it's just ignoring it? I can hardcode iptables 53 routing but then match domain feature does not work.

To Reproduce

Steps to reproduce the behavior:

  1. Connect 2 peers
  2. Use one of the peer as the custom dns host (it's VPN address)
  3. Check netbird status -d on both peers
  4. You can switch the peers, result will be similar but with the other peer

Expected behavior

I guess there Netbird should take care of it without sacrificing the features?

Are you using NetBird Cloud?

No, self-hosted.

NetBird version

0.54.2

Is any other VPN software installed?

No.

Debug output

Some output from both peers

This is the peer that is not hosting DNS server

Nameservers:
  [100.114.251.48:53] for [eee.anon-SHePr.domain] is Available
  [1.1.1.1:53, 1.0.0.1:53] for [.] is Available

Peer with DNS server hosted

Nameservers:
  [1.1.1.1:53, 1.0.0.1:53] for [.] is Available

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 @nmapx on GitHub (Aug 15, 2025). **Describe the problem** Possible bug? Hosting custom DNS server on one of the peers causes this peer not using this DNS server in local resolver. For some reason if peer receives it's own IP address in DNS configuration it's just ignoring it? I can hardcode iptables 53 routing but then match domain feature does not work. **To Reproduce** Steps to reproduce the behavior: 1. Connect 2 peers 2. Use one of the peer as the custom dns host (it's VPN address) 3. Check `netbird status -d` on both peers 4. You can switch the peers, result will be similar but with the other peer **Expected behavior** I guess there Netbird should take care of it without sacrificing the features? **Are you using NetBird Cloud?** No, self-hosted. **NetBird version** `0.54.2` **Is any other VPN software installed?** No. **Debug output** Some output from both peers This is the peer that is not hosting DNS server ``` Nameservers: [100.114.251.48:53] for [eee.anon-SHePr.domain] is Available [1.1.1.1:53, 1.0.0.1:53] for [.] is Available ``` Peer with DNS server hosted ``` Nameservers: [1.1.1.1:53, 1.0.0.1:53] for [.] is Available ``` **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 - [x] 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 2025-11-20 07:05:31 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2190