📺 Here's the long version of this!
https://blossom.primal.net/50dbafbf1aa6c6807de97fb140a2e4246f0878c7c51a48950144fe6e1981e130.mp4
So if I understand correctly, the DNS record is served to clients outside of the LAN by a Nostr relay. Then are able to access your local DNS server securely and then not have to route Nostr traffic through the DNS racket?
The big thing here though is the initial request for the DNS a record is still using DNS initially, right?
In this scenario the webserver has an npub identity and self-announces it's IP address + self-signed cert.
My machine does indeed connect to public relays to get his record event.
Yes, the browser does indeed use DNS like it does normally, except it passes through my nostr-compatible local DNS first.
I don't see an issue except if the DNS racket were not serving websocket server packets because they were afraid we were getting around their cabal. But then again, that would stop all Nostr notes, which seems...unlikely.
Great work, very clever work around.
Workarounds like this are nice because it integrates so well with existing system. Just the fact that this works system-wide opens up many doors.
Actually, I was thinking too small. Could this then in effect be used to serve the initial DNS A Record?
DNS bootstrap-> No-DNS cert validation
No-DNS bootstrap-> other No-DNS cert valid self hosted DNS servers?
Does that work? I might have confused myself.
