Use Cloudflare resolver for ACME DNS propagation check
Route DNS propagation checks through 1.1.1.1 only, bypassing the local resolver that caches stale responses and causes wildcard cert DNS-01 challenges to time out. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
beadcc5397
commit
6ae3f8be97
1 changed files with 2 additions and 2 deletions
|
|
@ -62,8 +62,8 @@ in
|
||||||
domain = "*.nordhammer.it";
|
domain = "*.nordhammer.it";
|
||||||
extraDomainNames = [ "nordhammer.it" ];
|
extraDomainNames = [ "nordhammer.it" ];
|
||||||
dnsProvider = "cloudflare";
|
dnsProvider = "cloudflare";
|
||||||
extraLegoRunFlags = [ "--dns.propagation-wait" "30s" ];
|
extraLegoRunFlags = [ "--dns.resolvers" "1.1.1.1:53" ];
|
||||||
extraLegoRenewFlags = [ "--dns.propagation-wait" "30s" ];
|
extraLegoRenewFlags = [ "--dns.resolvers" "1.1.1.1:53" ];
|
||||||
credentialFiles = {
|
credentialFiles = {
|
||||||
"CF_DNS_API_TOKEN_FILE" = "/var/secrets/cloudflare-token";
|
"CF_DNS_API_TOKEN_FILE" = "/var/secrets/cloudflare-token";
|
||||||
};
|
};
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue