i finally have the perfect use case for my notwebsite.com domain
Introducing my new open source #nostr freedom project - DNSPub
The key idea is that any DNS domain owner, with minimal changes, can enable any to npub be part of the domain name system, using signed DNS records published to relays.
For example, [npub].example.com would resolve to an IP address, and pass all the CA root program tests so that https://[npub].example.com could be a valid website in the browser.
Thanks to nostr:npub1s0veng2gvfwr62acrxhnqexq76sj6ldg3a5t935jy8e6w3shr5vsnwrmq5 and nostr:npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr for the idea!
#dnspub
Discussion
I am working on multi-domain support - in a week or so, I should be able to tell you what records to add to your registrar and it should be enabled.
Hell yes.
Just so I understand, there would still be the sole service running that answers those DNS queries (your service), right? The additional domain "mirrors" would provide backup domains, but not be providing an additional resolver service.
Down the line I'd like to be running another resolver, as well.
The DNS system is incredibly resilient and secure. I am actually leveraging DNSSEC which validates your domain name, then at the last moment I make a jump to an “insecure” (not really) subdomain “nub” where all the npubs hang off. Your subdomain can point to multiple redundant name servers, so if any of them go down, it just keeps on ticking. In the end, I’m just leveraging the security of DNS and IP, the way it was designed to be. I just wrote a DNS server that resolves records from signed events, instead of zone files. The simple idea - is that any npub can have its own DNS records and be a first class citizen of DNS.