2 ms·
> 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
by 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.