not yet, but we are waiting for somebody to go deep into it. nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c and I tried a kind:30053 for DNS records many months ago. The goal back then would be to not have a relay list with domain names, but a relay list with pubkeys that in turn point to IPs. Maybe he is still offering that event for his relays. We just never really went for it.
Discussion
Very interesting.
I would give it a go but:
1. I can barely understand anything about nostr. There's still quite a learning curve for me.
2. I only just started my relay yesterday and I can't even get that working properly yet.
And funny enough, one of the problems I have is cloudflare dns.
Get rid of Cloudflare:
https://simplifiedprivacy.com/cloudflare/
The modern internet is totally corrupt.
Only DNS can mildly slow down Nostr at this point. And that is a short amount of slowing down. People could edit their relays and go on. In that case yes, having a Nostr Naming System would be cool to have as a fallback option. Then enough fallbacks later, it could be default.. .
nostr:note1n480q2mva32hkdqd8xm3vl0d630luz8850smt87tp46w7fm4vnjquqnaqs
Current 30053 records point to old IPs. I can create new 30053 records if you want to play..
Nostr Naming System, a true DNS (Decentralised Name System)
🫂