Damus
saibeaks profile picture
saibeaks
@saibeaks
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
3❤️4
Anonymous Bananamous · 1w
I’m honestly at a loss but am going to follow you so I can watch you in anticipation of solving this. 🤩
Johnny · 1w
nostr:nprofile1qqsd3jykckhsfd6vhqlk5xkuqqcdcthyndq7klqqgwyqskympqd4swct9cj9d for the dns half, powerdns or coredns both take record writes over an http api and run fine in a container, and bind with nsupdate over rfc2136 is there if you want the plain standard. for the private ca, step-ca from small...
MMOnostr · 1w
Closest existing protocol pattern for "npub bound to a DNS-reachable identity" is NIP-05 (.well-known/nostr.json — maps a domain to a pubkey), which is most of what you're describing for step 2. For node discovery specifically, we ship NIP-66 on our own relay — a signed Nostr event (kind:30166) ...