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 !
I love those!
The most impressive one I saw, was IP over DNS.
You may be talking about iodine: https://code.kryo.se/iodine/
You can host it yourself.
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.:
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/
At some point I had a binary for the iodine client stored as DNS records, and another DNS record with a shell script that would fetch and decode them.
That's well known in exfiltration botnets.
I read about it years ago. Someone used a free Microsoft internet connection to activate their Windows.
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.
The opposite way from yesterday: https://news.ycombinator.com/item?id=22790425
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.
I just meant opposite in the most trivial sense:
finally my lisp class has aided me in a real-life scenario
I never had a lisp class, so I'm sitting here wondering why there is one single quote.
to prevent evaluation.
Otherwise the single-unquoted ( would be treated as a function call.
That's a reader macro to make it quoted.
What that means is 'don't try to evaluate this as a function call'.
Basically it's a data list.
Out of curiosity, did the sibling replies to your comment (all of which are accurate!) answer your question, in the sense that you now understand?
I'm glad my functional programming classes used Haskell instead:
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.
Would it be possible to support returning a larger excerpt of the article within a single TXT record?
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.
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.
Looks like my weekend got more interesting
$ dig dns.wpodns.adtac.in txt
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..."
Couldn’t this actually be useful in countries that block Wikipedia?
Not really, since it only returns a small section of the queried article.
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.
bing search returns wikipedia articles too. i suppose this works because bing is doing the filtering, and it can block based on content
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.
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.
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".
A true Rube Golberg machine.
Nice. Now let’s get Wireguard over DNS and be done with it.
How about WireGuard over DNSSEC and call it a day?
this is great. DNS TXT records are under appreciated. It's a distributed key value store with distributed caching
I had never thought of it that way. What is a practical use for using TXT records a distributed KV store?
distributed config.
Great start, but plain text in 2020?
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.
Whoa hold your horses! DGML first.
I'll contribute only if it allows third party cookies and all kinds of tracking
How do we approach embedding of proprietary content formats? We need some DDRM right?
I'll have to say that DTML seems to be a mess and missing the point and suggest we start working on XDTML.
XDTML 2.0 you mean? XDTML 1.0 is merely a serialisation of DTML. With XDTML 2.0 in place, the real fun can start!
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.
Now do it for stack exchange sites :)
dig how-do-i-block-edit-in-vim.wpodns.adtac.in txt
I think you meant how-do-i-exit-vim.wpodns.adtac.in
:exec system("dig how-do-i-exit-vim.wpodns.adtac.in txt +short| tr -d '\"'")
There are a few examples in rubydns code eg. https://github.com/socketry/rubydns/blob/master/examples/wik...
A few other implementations of "DNS as database":
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
The other day, while I was messing with Letsencrypt TXTDNS auth I was wondering:
Is there a problem with updating DNS TXT records too often?
It could become an interesting way to create a "decentralized" microblogging network.
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 !
I actually made this same thing recently: https://github.com/easrng/wiki-pdns