Hacker News Reader

Comment by shtrophic | Hacker News Reader

Last time I checked it couldn't do ipv6... in 2026?

Could be intentional: German privacy advocates really like that the limited ipv4 pool forces reusing IPs and prevents accidental imprinting a practically static address on a device.

Makes a lot of sense.

But self-hosting still require at least a public domain name [0], so here goes your privacy right?

- [0] https://docs.netbird.io/selfhosted/selfhosted-quickstart#inf...

> The VM must be publicly accessible on TCP ports 80 and 443, and UDP port 3478.

> A public domain name that resolves to the VM’s public IP address.

Since it already uses DNS it's disappointing that it hardcodes ports instead of using SRV records. IMO anything that can use SRV records should. It makes for a more robust internet.

The number of products that actually use SRV records is surprisingly low (besides some mailservers and kerberos)

Can't do IPv6 internally or externally? Internally there should be zero need for ~infinite addresses. Externally though I certainly hope all software is capable of operating via IPv6 at this point because otherwise it will only be increasingly broken.

Can't do it externally, kinda. Last year I succeeded in joining a device reachable only through IPv6 to a Netbird network, but their service would fail when I tried to configure IPv6 nameservers for it; the web UI did accept them fine though, they just didn't work. A shame, since I was otherwise fine with IPv4-only for the Netbird network.

IPv6 is coming soon to NetBird.

Reply on news.ycombinator.com