1
0
Fork 0
kubernetes/cert-manager
Dustin 4106038fe9 cert-manager: Use recursive resolver for checks
I've completely blocked all outgoing unencrypted DNS traffic at the
firewall now, which prevents _cert-manager_ from using its default
behavior of using the authoritative name servers for its managed domains
to check poll for ACME challenge DNS TXT record availability.
Fortunately, it has an option to use a recursive resolver (i.e. the
network-provided DNS server) instead.
2025-06-21 13:55:23 -05:00
..
.gitignore cert-manager: Add DNS.01 solver using Cloudflare 2023-05-09 21:13:08 -05:00
cert-exporter.config.yml cert-manager: Add cert for apps.du5t1n.xyz 2024-11-05 07:04:27 -06:00
cert-exporter.yaml cert-manager: Add cert for apps.du5t1n.xyz 2024-11-05 07:04:27 -06:00
certificates.yaml cert-manager: Add cert for apps.du5t1n.xyz 2024-11-05 07:04:27 -06:00
cluster-issuer.yaml cert-manager: Drop acmeDNS solver 2023-08-28 12:00:23 -05:00
dch-ca-issuer.yaml cert-manager: Configure ACME DNS.01 for dch-ca 2024-12-09 17:58:43 +00:00
kustomization.yaml cert-manager: Use recursive resolver for checks 2025-06-21 13:55:23 -05:00
secrets.yaml cert-manager: Configure ACME DNS.01 for dch-ca 2024-12-09 17:58:43 +00:00
ssh_known_hosts cert-manager: cert-exporter: Static SSH host keys 2024-01-04 15:35:00 -06:00