Post #2563468
2026-05-10 23:38 UTC
@jima@mspsocial.net @ryanc@infosec.exchange @owen@mastodon.transneptune.net Yep, that's the right way to do it.
Prior to DNS-PERSIST-01 announcement, I had an even fancier plan in the works: delegating _acme_challenge to a public server (run as a public service) with a DS whose key is held by your device that wants certs. When you need to do the ACME dance, the device would send a DNS packet to the public service, which would cache and serve it for up to some short time limit.
I never got around to implementing it, and once DNS-PERSIST-01 was announced, I dropped the idea because it's no longer needed.
Replies (1)
-
@jima@mspsocial.net 2026-05-11 00:49
@dalias@hachyderm.io @ryanc@infosec.exchange @owen@mastodon.transneptune.net In my case, the delegated server is PowerDNS with an SQL backend, and my validation hook script just adds a row to the records table, remotely over TLS (which is itself provided by a Let's Encrypt cert 😅).