Johnny Bergström
Johnny Bergström
Hey guys. Now I'm having an issue with letsencrypt as well. In my setup, I'm using Kubernetes and cert-manager from jetstack. This works great, it can generate the certificate via...
Having a reload ever X hours would work, but it would have to restart a lot more often than the TLS cert file changes since it can't know the difference...
Doesn't this create unnecessary interruptions to client requests? You would prefer to have one global option that restarts for example every hour instead of only when Corefile, tls, or zonefiles...
Sure that would be convenient, but more complicated. And it wouldn't work when you have more than one instance. I would somehow need to share persistent storage between my coredns...
But i guess this can be done from an external plugin as well.
I'm also a bit hesitant if it fits in this project. I'm running multiple coredns on the same kubernetes cluster with a DNS challenge served by cert-manager. Then coredns just...
That’s a great idea. Only one routine needed and possibly less restarts. As for HTTP challenges, I suppose if we refactor the DoH “is valid request” a little bit further,...
I'd say it's not related since this issue is also apparent when only one nameserver is listed and the warning in #989 is not shown. Also this is only one...
@pwrdwnsys did you go ahead to try to implement something for blocking lists of domains in trust-dns? Any suggestions on where to start? I'm new to both rust and trust-dns...