certbot already has a "stand-alone" authorization mechanism that has all those drawbacks, so doing a similar thing for DNS might not be too terrible... kro poi

certbot already has a "stand-alone" authorization mechanism that has all those drawbacks, so doing a similar thing for DNS might not be too terrible... kro pointed out (in this thread) this plugin that is more or less what I described: https://github.com/pawitp/acme-dns-server https://github.com/pawitp/acme-dns-server