Unrelated comment: I like this sort of web design. Might just be nostalgia. It reminds me of web design circa 2001 or so. You can see many similar examples on OSWD, e.g.:
I wouldn't say it's the opposite. It sounds the opposite from the title, but this actually returns Wikipedia content. The other one fetches a link to a site.
But! That solution made http requests (obviously), however you can in theory replace its queries with the thing in the current post and have true DNS-over-Wikipedia via the DNS protocol.
Large single record seems to work fine testing from BIND via Windows nslookup as long as you obey the 255 character per line rule i.e. split strings "like" "this" at least every 255 characters.
dns.wpodns.adtac.in. 3600 IN TXT "The Domain Name System (DNS) is a hierarchical and decentralized naming system for computers, services, or other resources..."
Those countries would just block adtac.in recursively when they noticed.
And if you decide to work around that by setting up more domains to do this, then you could just as well use those domains to front regular proxy servers.
A while back I showed how you could drop data into a server log file, and jokingly called it CurlyTP. I have thought many times about embedding a website directly into DNS.
For some reasons I always had the idea of using HTTP headers and server logs to pass data. It can, e.g., be an alternative way of passing request/query input to a server, instead of using URLs or HTML forms. The server can read filtered input from a log file stored on RAM disk.
I did the TXT record as HTML idea many years ago by modifying djb's dnstxt to output valid HTTP header. The idea was to use tinydns and dnscache as a "back-end" database to store millions of tiny "webpages".
I propose we design a markup language so this can be parsed. How about DTML? And maybe some styling rules as well, we can call it DSS. And we can't forget a basic scripting language called DJS.
I'll start working on the parser, we can call it a drowser.
I think plain text is OK. There is also Markdown, MediaWiki format, etc, although a simple readable format is best, so that includes plain text (and possibly Markdown too).
And even if another format is made, we should avoid the mistakes of HTML, such as scripting and styling and some other stuff.
"A globally-distributed, eventually-consistent, 100% available key-value store ;)" (I haven't actually tried running this code personally): https://github.com/craftyphotons/ten34
That’s really cool ! A security teacher told me a long time ago about these possibilities and I love the concept, I love Wikipedia and I love plain text, so thanks a lot for this !
47 comments
[ 4.1 ms ] story [ 95.0 ms ] threadThe most impressive one I saw, was IP over DNS.
You can host it yourself.
http://www.oswd.org/design/preview/id/9/
http://www.oswd.org/design/preview/id/3/
http://www.oswd.org/design/preview/id/6/
http://www.oswd.org/design/preview/id/45/
The connection only allowed access to MS activation servers, but also DNS.
The DNS would resolve any domain, even the ones that don't belonged to MS, so they could use it to get data out.
I told this story to a few people in my time, all working in IT, and all thought I was bullshitting them, like I was some crazy conspiracy theorist.
And now I'm reading that this is a well known technique and there are even libraries doing this.
What that means is 'don't try to evaluate this as a function call'.
Basically it's a data list.
You should be able to get up to 64 KiB (minus a few bytes for headers, etc) within a TXT record. The lookup will have to use TCP though.
Looks like my weekend got more interesting
dns.wpodns.adtac.in. 3600 IN TXT "The Domain Name System (DNS) is a hierarchical and decentralized naming system for computers, services, or other resources..."
And if you decide to work around that by setting up more domains to do this, then you could just as well use those domains to front regular proxy servers.
https://miscdotgeek.com/curlytp-every-web-server-is-a-dead-d...
Anybody up for the challenge? With some scripting you could do a dig on a TXT record, parse it, and display it right in a web page.
I did the TXT record as HTML idea many years ago by modifying djb's dnstxt to output valid HTTP header. The idea was to use tinydns and dnscache as a "back-end" database to store millions of tiny "webpages".
A true Rube Golberg machine.
I propose we design a markup language so this can be parsed. How about DTML? And maybe some styling rules as well, we can call it DSS. And we can't forget a basic scripting language called DJS.
I'll start working on the parser, we can call it a drowser.
And even if another format is made, we should avoid the mistakes of HTML, such as scripting and styling and some other stuff.
dig how-do-i-block-edit-in-vim.wpodns.adtac.in txt
DNS-FS: https://blog.benjojo.co.uk/post/dns-filesystem-true-cloud-st...
DNS as a config management database: https://www.lastweekinaws.com/podcast/aws-morning-brief/whit...
"A globally-distributed, eventually-consistent, 100% available key-value store ;)" (I haven't actually tried running this code personally): https://github.com/craftyphotons/ten34
Is there a problem with updating DNS TXT records too often?
It could become an interesting way to create a "decentralized" microblogging network.