HTML over DNS
A web client retrieves page content from DNS answers while a conventional server supplies the surrounding page, blurring lookup and content delivery.

This experiment uses a web page as a client for DNS-hosted content. The browser still loads a conventional shell, but the page body comes from DNS answers.
It blurs the line between naming service and content platform. It also shows why careful limits, caching, and escaping matter when DNS becomes an application backend.
Primary source: https://news.ycombinator.com/item?id=28218406