zerotier
zeronsd does not handle subnet changes well
Reproduction:
- Create a network
- configure zeronsd to use that network with two authorized members
- change the subnet and trash the old addresses
Congratulations, your server is now unusable until restart.
Will get to this over the next few weeks.
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 assigned to that interface. If that occurs, gracefully terminate non-zero to force a restart by the supervisor.
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 to resolve trivially with the current state of things.
Basically, if you do this; restart your zeronsd instance.
had to delete old addresses manually from the memeber list, then restart the zeronsd instance, and the dns resolution works
