Alright, it works now. Seems to have taken extra long (even though dig and nslookup gave the correct DNS)
your dns might have updated but other folks isp dns etc might not
you can use both
to test domain A record propagation across several geographically disperse dns servers
guess one of my concerns outlined at The server could not resolve a domain name
Got the same error, check log below
Debian 7 Apache2.
Used:
./letsencrypt-auto --apache --server https://acme-v01.api.letsencrypt.org/directory --agree-dev-preview
These all claimed it was on route 53 when I ran the test.
Thank you all for your patience. The team landed some improvements over the weekend that we are hoping will solve a majority of these errors.
These are DNS timeouts as a percentage of total DNS lookups, as part of the Boulder validation process, for both production and staging:
While the error rate has dropped near zero for the last 36 hours, we expect to still encounter the occasional DNS timeout. Ultimately, we still may have packet loss from one or more of our datacenters to your authoritative nameserver, after all.
At any rate, thanks for your patience as we worked through this.
6 Likes
excellent to see and hear @jcjones 
My apologies for not posting much earlier, those issues are (long) solved. Thanks to the team behind Lets Encrypt.
I’m getting the same from many hours. Currently is impossible to issue certificates from staging or production.
I don’t know if its’ related, but i’m trying to issue a multi-domain certificate (about 20-25 domains)
I obtained certs around that time without issue ( and more recently). Are you still having issues ? if so is it failing on the first domain or later ? and what is in the full log at that time ?