4 ms·
There has never been any limit to what one can put in a DNS RR. From the year 2000, 42 ways to distribute arbitrary data over the internet, including DNS: htt
by 1vuio0pswjnm7 6y ago
There has never been any limit to what one can put in a DNS RR.
From the year 2000, 42 ways to distribute arbitrary data over the internet, including DNS:
http://web.archive.org/web/20001207014600/http://decss.zoy.org:80/ http://web.archive.org/web/20001207014600/http://decss.zoy.o...
djbdns has always allowed arbitrary characters in TXT records. I have put HTML in TXT records to serve mini web pages over UDP. People have put speex files in RRs. Not sure "BIND" or other popular DNS servers of the day allowed such flexibility. Nowadays it is easy to find such software.
Someone will probably comment on tunneling over DNS or Wikipedia over DNS.
This is why ICANN DNS and its use of DNSSEC always seemed wrong to me. If it's someone else's data, ICANN should not have the power to instantly "invalidate" it. Resurgence of DNSSEC was in part a response to the idea that shared caches are vulnerable, but DNS is more than just shared caches; and the way DNSSEC is used in practice relies on the strange assumption that ICANN is the self-appointed arbiter of "official" domain names. But as you can see DNS, the protocol, can be used for more than simply "official" ICANN-approved domain names.
- elliottinvent 6y ago> From the year 2000, 42 ways to distribute arbitrary data over the internet, including DNS This is very cool, thanks for the link. Would be interested to hear more about your experience in storing HTML in DNS.
- 1vuio0pswjnm7 6y agoPeople have now wrapped DNS RR in TLS, then in HTTP and they are thinking about putting DNS RR into HTTP headers or into HTML tags. https://www.potaroo.net/ispcol/2020-06/row.html https://www.potaroo.net/ispcol/2020-06/row.html In the late 2000's I took the oppsoite approach, because back then, DNS, i.e., traditional 512K UDP packets, was much faster for data retrieval than TCP/SSL/HTTP. TLS has gotten quite fast but using UDP is still faster, that's why we see UDP-based "reliable transport" protocols like (lesser known) CurveCP and (better known) QUIC. I put the content into the DNS RR instead of putting the DNS RR, e.g., IP address, into the content. Retrieving content, e.g., a web page, has become a two-step process, thanks to DNS. It could be a one step process if we used IP addresses instead of names; I still do this where possible. However to use names, first we have to get the IP address (step 1), and only then can we retrieve the content (step 2). If we combine the IP address with the content then we can eliminate a step. Putting everything into DNS instead of into web pages gives more control to the user, IMO. Web browsers are controlled by companies that rely on the survival of the online ad industry. DNS software does not have this problem.
- 1vuio0pswjnm7 6y agos/512K/512/
- inopinatus 6y agoQuite so. Or as one eminent commentator put it, back in 2011: https://twitter.com/DEVOPS_BORAT/status/137607246036213760 https://twitter.com/DEVOPS_BORAT/status/137607246036213760
- jeroenhd 6y ago> But as you can see DNS, the protocol, can be used for more than simply "official" ICANN-approved domain names. The fact that it can be used to transfer HTML or Speex files doesn't mean it should be used to do so. DNS is developed to serve one purpose, and that's to resolve domain names and domain information. Arbitrary data transfers over DNS were never its intended purpose so of course the designers to DNS extensions don't take DNS tunneling into account. For example, the iCal protocol allows for arbitrary amounts of information through a comment on each calendar item. However, if I start sending calendar events between devices to stream video, I don't expect the next iteration of the standard to support my use case. The presence of a general purpose information field does not necessarily mean that this field should be expected to serve any purpose unrelated to the problem the protocol was designed to solve. There's little preventing you from using your own DNS client with different DNSSEC keys for validation of your own records if you're using an alternate domain name registration system. ICANN has always been the de facto standard for TLDs and therefore domain names so putting the general DNSSEC keys with them makes sense.