Closed hvisage closed 2 years ago
Thanks for the question! (FYI we are also tracking this same question in the forums: https://caddy.community/t/forcing-certmagic-to-use-system-resolvers-for-propagation-checks/15690?u=matt)
As noted in the Caddy forum thread, DNS propagation check is done by certmagic. Any option to resolve records differently or even to disable the propagation check would have to be implemented there, this plugin doesn't have that kind of control. Closing the issue.
As noted in the Caddy forum thread, DNS propagation check is done by certmagic. Any option to resolve records differently or even to disable the propagation check would have to be implemented there, this plugin doesn't have that kind of control. Closing the issue.
Which is contradicting the Caddy/Certmagic forum statement ;(
https://caddy.community/t/forcing-certmagic-to-use-system-resolvers-for-propagation-checks/15690/6 That’s not for Caddy/Certmagic to control, I think, it’s up to the acmedns plugin to control how that’s resolved.
System inside a protected environment where only proxied HTTPS is allowed to specific sites (like LetsEncrypt) Only single DNS resolver allowed (firewall)
It seems it tries to do a direct DNS lookup against the acmedns.io servers, instead via the system resolvers, even when "forced" in the config file, and thus times out without continuing ;(
Caddyfile: