Several people are reporting that the staging server is having DNS trouble again.
Issuing certificates from the staging server (e.g. with certbot --dry-run) will fail with DNS problem: query timed out looking up A for example.org. The production server is not affected.
And I can reproduce as well.
/ping @lestaff
Thanks. Looking into it
Hello,
We have an issue with getting new certificates for our servers. It seems that this happened before and there is another thread about it.
As you can see below:
"detail": "DNS problem: query timed out looking up A for server1.test20.simplyspamfree.com",
"status": 400
# letsencrypt -v --debug --staging certonly -a standalone -t --agree-tos --email email@email.com -d server1.test20.simplyspamfree.com --csr csr.der --fullchain-path fullchain.pem --keep
Please do note that this is on staging.
Also, as you can see these queries are fine from other DNS servers:
https://mxtoolbox.com/SuperTool.aspx?action=a%3Aserver1.test20.simplyspamfree.com&run=toolpage
http://dnscheck.pingdom.com/?domain=simplyspamfree.com
https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/599adce39ccf8f190500077b
We’re actively working on resolving the staging disruption.
This issue should now be resolved. Please let me know if you’re still having trouble issuing certificates from the staging environment. I apologize for the disruption 
A post was split to a new topic: Error reaching production API
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.