Regarding some questions about relay-dns certificates.
Regarding some questions about relay-dns certificates.
I'm currently building iroh dns/iroh relay services (both self-built and not using any official iroh services).
I've noticed that iroh relay has a reload mode, which reloads certificates daily. I use the allsll project to automatically manage and renew my certificates. This works perfectly with the reload mode.
However, I still need the iroh dns service. I use manual mode in iroh, but why doesn't iroh dns offer a refresh feature? I can certainly use some automated scripts on the server to restart the server at a specified time. But I'm wondering why this design was adopted, or if this feature hasn't been added yet?
I ideally want relay | dns to have a similar certificate management system, including physical location and mode, to facilitate management. I don't understand why dns doesn't offer automatic reloads.
As for why I don't use LetsEncrypt mode, my server also has a separate HTTPS service, as we only support HTTP and TLS-ALPN both challenges, but both challenges require the use of ports 80 and 443, but the service bound to iroh dns happens to require these two ports, so I can only use the dns challenge, but tokio-rustls-acme does not support the dns challenge.