Wouldn't it be useful to have a censorship-resistant layer for normie DNS? Controlled from Nostr.
#asknostr #devstr #dns
Without going too much into design details, npubs that used to have their val...
It'd also be nice to have some kind of `protectfromtakedown.me` landing page, for new or existing npubs, that helps to set up NIP-05 and distribute kind 0 events to the NIP-66-discovered dns-specialized relays. This could be a static page, served from the dns-specialized relay itself, that contains a pre-fetched list of relays this relay is already aware of.
Takedown identification should be taken with care and with continued maintenance. AI-based monitoring and automatic issue creation are possible: news could be monitored for new domains; tests could be run for new domains. All this stuff should be deployed far away from the centralized stuff like GitHub's CI from the very beginning.
All kinds of tricks are possible. I'd normally expect `serverHold` domain status (this happened to `t.me` and `annas-archive.org`), but it could also be a weird nameserver behavior (this happened with `gmailnator.com`, looks like google attached their nameservers that currently return `SERVFAIL`):
```
$ dig @1.1.1.1 gmailnator.com
; <<>> DiG 9.18.42 <<>> @1.1.1.1 gmailnator.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61131
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation gmailnator.com.)
; EDE: 23 (Network Error): ([2001:4860:4802:36::63]:53 returned REFUSED for gmailnator.com A)
;; QUESTION SECTION:
;gmailnator.com. IN A
;; Query time: 628 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Sun Aug 09 01:59:24 MSK 2026
;; MSG SIZE rcvd: 148
```
Or it could be a non-weird nameserver behavior as well; Google could just resolve a normal IP and that would possibly be even more puzzling to identify.
Takedown identification should be taken with care and with continued maintenance. AI-based monitoring and automatic issue creation are possible: news could be monitored for new domains; tests could be run for new domains. All this stuff should be deployed far away from the centralized stuff like GitHub's CI from the very beginning.
All kinds of tricks are possible. I'd normally expect `serverHold` domain status (this happened to `t.me` and `annas-archive.org`), but it could also be a weird nameserver behavior (this happened with `gmailnator.com`, looks like google attached their nameservers that currently return `SERVFAIL`):
```
$ dig @1.1.1.1 gmailnator.com
; <<>> DiG 9.18.42 <<>> @1.1.1.1 gmailnator.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 61131
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; EDE: 22 (No Reachable Authority): (at delegation gmailnator.com.)
; EDE: 23 (Network Error): ([2001:4860:4802:36::63]:53 returned REFUSED for gmailnator.com A)
;; QUESTION SECTION:
;gmailnator.com. IN A
;; Query time: 628 msec
;; SERVER: 1.1.1.1#53(1.1.1.1) (UDP)
;; WHEN: Sun Aug 09 01:59:24 MSK 2026
;; MSG SIZE rcvd: 148
```
Or it could be a non-weird nameserver behavior as well; Google could just resolve a normal IP and that would possibly be even more puzzling to identify.
4
