Error configuring IPv6 nameservers #2032

Open
opened 2025-11-20 06:11:31 -05:00 by saavagebueno · 3 comments
Owner

Originally created by @amongonz on GitHub (Jun 30, 2025).

Describe the problem

Trying to add an IPv6 nameserver (e.g. Cloudflare) results in invalid address strings, with the following output from netbird status -d:

Nameservers: 
  [2606:4700:4700::1111:53, 2606:4700:4700::1001:53] for [.] is Unavailable, reason: 2 errors occurred:
        * with udp: dial udp: address 2606:4700:4700::1111:53: too many colons in address
        * with udp: dial udp: address 2606:4700:4700::1001:53: too many colons in address

To Reproduce

Steps to reproduce the behavior:

  1. Add an IPv6 nameserver to a group from the NetBird dashboard.
  2. Run netbird status -d on a group peer.

Expected behavior

The address strings are formatted and configured correctly. Presumably, the output should have been [2606:4700:4700::1111]:53 and [2606:4700:4700::1001]:53.

Are you using NetBird Cloud?

Yes.

NetBird version

0.49.0

Is any other VPN software installed?

No.

Additional context

A similar issue was already closed as completed in the past, https://github.com/netbirdio/netbird/issues/2327.

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 (N/A)
  • Checked firewall settings (N/A)
Originally created by @amongonz on GitHub (Jun 30, 2025). **Describe the problem** Trying to add an IPv6 nameserver (e.g. Cloudflare) results in invalid address strings, with the following output from `netbird status -d`: ``` Nameservers: [2606:4700:4700::1111:53, 2606:4700:4700::1001:53] for [.] is Unavailable, reason: 2 errors occurred: * with udp: dial udp: address 2606:4700:4700::1111:53: too many colons in address * with udp: dial udp: address 2606:4700:4700::1001:53: too many colons in address ``` **To Reproduce** Steps to reproduce the behavior: 1. Add an IPv6 nameserver to a group from the NetBird dashboard. 2. Run `netbird status -d` on a group peer. **Expected behavior** The address strings are formatted and configured correctly. Presumably, the output should have been `[2606:4700:4700::1111]:53` and `[2606:4700:4700::1001]:53`. **Are you using NetBird Cloud?** Yes. **NetBird version** 0.49.0 **Is any other VPN software installed?** No. **Additional context** A similar issue was already *closed as completed* in the past, https://github.com/netbirdio/netbird/issues/2327. **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 (N/A) - [ ] Checked firewall settings (N/A)
saavagebueno added the bugipv6clientdns labels 2025-11-20 06:11:32 -05:00
Author
Owner

@nazarewk commented on GitHub (Jun 30, 2025):

NetBird doesn't support internal IPv6 addressing or routing yet, please follow https://github.com/netbirdio/netbird/issues/46

I believe the linked issue was related to establishing external connections to IPv6 addresses, which does work right now.

I'm closing on behalf of https://github.com/netbirdio/netbird/issues/46 , but will reopen if you believe it's something else.

@nazarewk commented on GitHub (Jun 30, 2025): NetBird doesn't support internal IPv6 addressing or routing yet, please follow https://github.com/netbirdio/netbird/issues/46 I believe the linked issue was related to establishing external connections to IPv6 addresses, which does work right now. I'm closing on behalf of https://github.com/netbirdio/netbird/issues/46 , but will reopen if you believe it's something else.
Author
Owner

@amongonz commented on GitHub (Jun 30, 2025):

The IPs in the example are Cloudflare's public nameservers, which are external, and I'm not using an exit node. I woudn't expect this setup to route internally for DNS, although I'm not familiar with netbird yet.

If this use case weren't supported, I guess I'd still be surprised to see the cloud dashboard validate the IPv6 addresses for the nameservers. Between that and the visible error being that the host part lacks brackets, I had assumed it was a client bug.

@amongonz commented on GitHub (Jun 30, 2025): The IPs in the example are Cloudflare's public nameservers, which are external, and I'm not using an exit node. I woudn't expect this setup to route internally for DNS, although I'm not familiar with netbird yet. If this use case weren't supported, I guess I'd still be surprised to see the cloud dashboard validate the IPv6 addresses for the nameservers. Between that and the visible error being that the host part lacks brackets, I had assumed it was a client bug.
Author
Owner

@nazarewk commented on GitHub (Jun 30, 2025):

thanks for clarification, I have asked the dev team about it. It might be a quick fix, but could also be something larger that would need to wait for #46 to be addressed.

@nazarewk commented on GitHub (Jun 30, 2025): thanks for clarification, I have asked the dev team about it. It might be a quick fix, but could also be something larger that would need to wait for #46 to be addressed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2032