-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloudflare-dns.com is too slow #3437
Comments
表示阿里云的国内服务器,这个地址现在不可访问了,导致证书check,一直报curl代理错误 |
解决了,编辑 acme.sh 替换这两个地方的代码 _ns_lookup_cf() { |
Hi ... in cron, where do we add option --dnssleep 300 In crontab ( crontab -l ) i have ;
Or do we have to re-request the certs manually and follow through ? |
Partial answer recived at ; |
Possible to add a command line override to point to the DNS server of your choice? I currently have to use the dnssleep option when we run acme.sh against our internal ACME RA and internal dns as the public DNS is unaware and usually the server running the client can't even reach the internet. If we could add like --dnscheck-server mydns.internal then I could still get the benefit of the client side validation / propagation with internal DNS. |
No, please use |
请查看这个 issue: |
When I issue new certificate, acme.sh request
https://cloudflare-dns.com/dns-query?name=_acme-challenge.my.domain&type=TXT
with curl. It takes about 15 minutes to get done for only 1 domain and after that acmesh throws some error in curl. I also tried to go to the cloudflare-dns.com manually from my PC browser and it won't load. Cloudflare Status says DNS lookup is operational in my region. Maybe switch to another dns lookup?The text was updated successfully, but these errors were encountered: