The DNS Museum

(dns.museum)

98 points | by zdw 2 days ago

8 comments

  • herbst 2 hours ago
    It looks very very vibe coded. Maybe try a different design approach, the idea generally sounds interesting
    • zimpenfish 49 minutes ago
      On the about page: "AI helped create this site, but I'm responsible for the content, so please let me know about any mistakes."

      (I know pgl has been collecting DNS weirdnesses for years - that bit definitely hasn't been AI-generated.)

  • cachvico 8 hours ago
    It's missing perhaps the most classic of all: someone hosted the DeCSS script (for bypassing the DRM in DVDs) in DNS around 2000.
  • user3939382 18 minutes ago
    I miss Granite Canyon :(
  • HelloUsername 5 hours ago
  • ktpsns 7 hours ago
    The various "VPN/IP over DNS" solutions miss a typical, more performance variant: VPN over UDP/53. Because DNS is frequently not filtered in badly locked down hotspots.
    • benjojo12 3 hours ago
      iodine automatically detects this and switches to boring IP encapsulation if this is the case
  • tazjin 8 hours ago
    At some point I hosted my blog in DNS; it was a bunch of chunks in TXT records which the frontend would reassemble. It had really strange side effects, e.g. editing a post could shuffle the chunks but then they'd end up being cached separately and some people would see weird artefacts in the text.

    I don't know why I did that, but it was fun!

  • commandersaki 5 hours ago
    How about a page for all those DNSSEC outages?

    https://ianix.com/pub/dnssec-outages.html

  • island_dev 6 hours ago
    A shameless plug for my own project where the DNS infrastructure plays a key role. The idea is to make a chain of TXT records where anyone with a domain name can join the chain my adding a TXT record pointing to the parent domain. https://recordrelay.net
    • rknightuk 4 hours ago
      This is cool and now I'm holding the baton.