Post #1661618

2026-03-26 12:54 UTC

Hey, y&#39;all! Just decided to finally post my IETF draft, that I&#39;ve been cooking up for the last few months, go check it out, roast me, maybe go implement it and show me your implementations :3 :boost_ok: Here&#39;s the abstract: This document specifies a mechanism for serving content, such as HTML or JSON, directly via DNS TXT records. This feature is intended as a fallback mechanism when a primary service (A/AAAA record) is unreachable, or as a lightweight hosting solution for parked domains to display landing pages without requiring active HTTP servers or individual SSL certificates. Trust is established via DNSSEC, allowing browsers to treat the content as secure. https://datatracker.ietf.org/doc/draft-dns-content-delivery/ https://www.ietf.org/archive/id/draft-dns-content-delivery-00.html

Replies (2)

@domi@donotsta.re 2026-03-26 13:08

@april i would like to see the future where this lands XD i feel like it’d have similar problems with adoption as JXL does the chunking is really neat. you should specify what the safe limit is (IME, around 42KB, but some networks have resolvers which can only go as high as the MTU minus packet overhead, or thereabouts. so tbf it would be cool to have a system to resize the chunks on the fly (so you store it as one metarecord, and it gets chunked on delivery by your DNS server)

Open ##1661622
@Mae@is.badat.dev 2026-03-26 13:13

@april Uninformed reply, I havent read the RFCI think if this was only used for fallback this might be ok, but I'm worried there are gonna be cases where this is the only option, and I don't think it's a good idea to force all http clients to also do DNS resolution Also doesn't dnssec have a completely different model compared to the "standard" root ca infra? I think security people wouldn't like that

Open ##1661626