A shameless plug for my own project where the DNS infrastructure plays a key role. The idea is to make a chain of TXT records where anyone with a domain name can join the chain my adding a TXT record pointing to the parent domain. https://recordrelay.net
The various "VPN/IP over DNS" solutions miss a typical, more performance variant: VPN over UDP/53. Because DNS is frequently not filtered in badly locked down hotspots.
At some point I hosted my blog in DNS; it was a bunch of chunks in TXT records which the frontend would reassemble. It had really strange side effects, e.g. editing a post could shuffle the chunks but then they'd end up being cached separately and some people would see weird artefacts in the text.
A shameless plug for my own project where the DNS infrastructure plays a key role. The idea is to make a chain of TXT records where anyone with a domain name can join the chain my adding a TXT record pointing to the parent domain. https://recordrelay.net
It's missing perhaps the most classic of all: someone hosted the DeCSS script (for bypassing the DRM in DVDs) in DNS around 2000.
The various "VPN/IP over DNS" solutions miss a typical, more performance variant: VPN over UDP/53. Because DNS is frequently not filtered in badly locked down hotspots.
At some point I hosted my blog in DNS; it was a bunch of chunks in TXT records which the frontend would reassemble. It had really strange side effects, e.g. editing a post could shuffle the chunks but then they'd end up being cached separately and some people would see weird artefacts in the text.
I don't know why I did that, but it was fun!
the site has an example of this. https://dns.museum/exhibits/blogging-via-dns