certimate-go / certimate-go/certimate
Globally set dnsPropagationWait and dnsPropagationTimeout
- Dominant language
- Go
- Stars
- 9.3k
- Forks
- 898
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 8
Description
### Release Version / 软件版本
v0.4.31
### Description / 问题描述
How can I globally set dnsPropagationWait and dnsPropagationTimeout?
I am using a custom ACME challenge endpoint based on HTTP request.
The DNS zone has a min TTL of 300. The docker DNS caches the DNS requests and even though the DNS zone already has the entry set, the docker DNS still has a cache that hasn't expired yet. I therefore get this error message:
```
[2026-08-24 09:36:16]
go-acme/lego: Deactivating authorization.
[2026-08-24 09:36:16]
could not obtain certificate
[2026-08-24 09:36:16]
failed to obtain certificate: resolver: one or more domains had a problem: [foo.example.com: dns01: time limit exceeded: last error: recursive nameservers: NS 127.0.0.11:53 returned NXDOMAIN for _acme-challenge.aliasforfoo.example.com.]
```
Setting the DNS TTL in the workflow was not enough, I had to set the DNS propagation delay. However, I have 15 workflows. I don't want to set these manually with every workflow. Can I set these values globally somehow?
Thanks!
### Miscellaneous / 其他
_No response_
Contributor guide
Research direction
Start by tracing how workflow settings reach the ACME challenge endpoint, focusing on dnsPropagationWait and dnsPropagationTimeout and the existing workflow configuration. Determine where a global setting could be represented, then verify that it applies consistently to all workflows and accommodates the Docker DNS caching case described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100