caddy-dns/cloudflare

could not determine the zone

masx200 opened this issue · 4 comments

masx200 commented 
2022/07/06 02:09:58.974 ERROR   tls.obtain      could not get certificate from issuer   {"identifier": "test.masx200.top", "issuer": "acme-v02.api.letsencrypt.org-directory", "error": "[test.masx200.top] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of _acme-challenge.test.masx200.top: could not determine the zone: unexpected response code 'SERVFAIL' for 7ux4q93992xmjqv8388a.dcv2.httpsauto.com. (order=https://acme-v02.api.letsencrypt.org/acme/order/619340006/104179459486) (ca=https://acme-v02.api.letsencrypt.org/directory)"}
2022/07/06 02:09:58.975 ERROR   tls.obtain      will retry      {"error": "[test.masx200.top] Obtain: [test.masx200.top] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of _acme-challenge.test.masx200.top: could not determine the zone: unexpected response code 'SERVFAIL' for 7ux4q93992xmjqv8388a.dcv2.httpsauto.com. (order=https://acme-v02.api.letsencrypt.org/acme/order/619340006/104179459486) (ca=https://acme-v02.api.letsencrypt.org/directory)", "attempt": 1, "retrying_in": 60, "elapsed": 29.786988, "max_duration": 2592000}
masx200 commented

I originally had a cname record from _acme-challenge.masx200.top pointing to 7ux4q93992xmjqv8388a.dcv2.httpsauto.com, when I delete it it's ok?

mholt commented

That could have something to do with it; I'm not sure. SERVFAIL means the DNS server failed, I think.

(Closing, as doesn't appear to be a problem with this module.)

masx200 commented

This may be related to cname records.