Toying with a small #network idea where new nodes in separate locations would self register their npub on DNS, ideally trigger a certificate generation by a private CA.
I imagine something like:
1. New node comes with nsec, npub. 2. Registers npub A record (also last 6 digits of npub, too) on "domain(.) com" DNS zone.
3. Maybe some SRV records to facilitate service discovery.
4. Other (known) nodes find the new node, wg to it, cool stuff happens.
5. Profit (joking).
There will be a couple of name resolvers that nodes will use to locate other nodes and services.
What I'm not sure about is what software I could use to update DNS records. Wishlist: lightweight, maybe container based. Bonus: standard API.
Has anybody approached this use case? How did you solve it? Software recommendations?
Nodes needn't know about Nostr, but this could be used in the backend. I'd like the frontend to be DNS, to minimise friction on devices that can't be *taught* Nostr. #asknostr
saibeaks
jon@saibeaks.com
npub1mryf...m80j
Came here for the technology, staying for the vision. #AFQU (backup: jon_bk@saibeaks.com) "Soyez réalistes, demandez l'impossible"
