Erik Hollensbe

@AndreKR libzt still needs some massage to play well with the rust async ecosystem, but I need to double check with the principal for that work. That was the plan...

I'm not sure I agree. Multiple TLDs implies some kind of partitioning and a rethinking of how the TLD is in relation to the individual addresses. How would you propose...

Sure, so here, on linux you can accomplish this really easily with systemd-networkd and systemd-resolved. If that's an option for you, try this package I slapped together over the weekend,...

eh, for example, I have a seafile at a TLD that is hosted by a local DNS service @ 10.0.0.x and on zerotier (with zeronsd) at some 172/16 address. both...

ahh I see. ok, I'm not going to be able to deal with this today but I will try to get to it within the next week or two. Thanks...

we're not going to alter the forwarding of records at all. there are so many uncanny security problems there that I don't have enough space to address in a github...

I'll look into it; thanks! ------- Original Message ------- On Wednesday, May 18th, 2022 at 5:58 PM, ato2 ***@***.***> wrote: > Version : 0.5.1-1 > After correcting a duplicate there...

this is likely because the listening IP changed from underneath it. I think the best solution for now is to detect when there are no known addresses that zerotier-one has...

I know I said "the next few weeks" but we all saw how that went. I'm going to leave this alone as a known issue for now, it'll be complicated...

Yes, or just using box in general as a generic build system. On Thu, Feb 16, 2017 at 1:56 AM, Ilya Dmitrichenko wrote: > So this would be to help...