📺 Here's the long version of this!

https://blossom.primal.net/50dbafbf1aa6c6807de97fb140a2e4246f0878c7c51a48950144fe6e1981e130.mp4

Reply to this note

Please Login to reply.

Discussion

This is amazing bro!

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.

Nice! Yes i think Nostr is the way to go on a lot of these networking challenges. We can clear out a lot of technical debt built up over the last 20 years.

or a standard browser with the option to enable nostr lookups

Neet

i'm stuck here

cd nodns-cli && make build

go build -ldflags "-X main.version=d06792e -s -w" -o build/nodns .

/bin/sh: 1: go: not found

make: *** [Makefile:53: build] Error 127

i'm an Idiot , ofc i had to install go doh

but i published my npub nostr:npub1ykal2phgzf6ljmql6l8khmf0ekf6ny0582r89m00j9vjt8qezhjqqpa3dl

with ip 192.168.201.174

dig {@localhost:5354}nostr:npub1ykal2phgzf6ljmql6l8khmf0ekf6ny0582r89m00j9vjt8qezhjqqpa3dl.nostr

no-dns server runs on port 5354

all well but the answer that came back

;; QUESTION SECTION:

;npub1ykal2phgzf6ljmql6l8khmf0ekf6ny0582r89m00j9vjt8qezhjqqpa3dl.nostr. IN A

;; Query time: 7 msec

;; SERVER: 192.168.201.70#53(192.168.201.70) (UDP)

;; WHEN: Fri Sep 26 14:32:33 CEST 2025

;; MSG SIZE rcvd: 87

came back with diff ip huh ?

ok i got it now and it works perfectly

dig @localhost -p 5354nostr:npub1ykal2phgzf6ljmql6l8khmf0ekf6ny0582r89m00j9vjt8qezhjqqpa3dl.nostr

nostr:npub1ykal2phgzf6ljmql6l8khmf0ekf6ny0582r89m00j9vjt8qezhjqqpa3dl.nostr. 3600 IN A 192.168.201.174

have some sites who use nostr domain name to test ?

Hello, I love this initiative. I have been working in the shadows on something that might interest you, it perfectly complements DNS over NOSTR, but my time is [zero] right now.

Can I send you a DM after Oct 15?

Regards!