Dustin a507fe1090 cert-manager: Switch to acme-dns ... Using the local name server as the authoritative server for ACME challenge records turned out to be quite problematic. For some reason, both Google and Cloudflare kept returning SERVFAIL responses for the *_acme-challenge* TXT queries. I suspect this may have had something to do with how BIND was configured to be the authoritative server for the *o-ak4p9kqlmt5uuc.com* while also being a recusive resolver for clients on the local network. Using *acme-dns.io* resolves these issues, but it does bring a few of its own. Notably, each unique domain and subdomain must have its own set of credentials (specified in the `acme-dns.json`) file. This makes adding new certificates rather cumbersome.		2023-05-01 20:57:24 -05:00
..
.gitignore	cert-manager: Switch to acme-dns	2023-05-01 20:57:24 -05:00
cert-exporter.yaml	cert-manager: Add cert-exporter CronJob	2023-05-01 20:57:22 -05:00
cert-manager.yaml	cert-manager: Install cert-manager	2023-05-01 20:22:35 -05:00
certificates.yaml	cert-manager: Add Pyrocufflink wildcard cert	2023-05-01 20:57:01 -05:00
cluster-issuer.yaml	cert-manager: Switch to acme-dns	2023-05-01 20:57:24 -05:00
kustomization.yaml	cert-manager: Switch to acme-dns	2023-05-01 20:57:24 -05:00