It appears that the letsencrypt servers did not resolve my domain.
All other subdomains produce the same error.
I use Cloudflare as DNS servers.
My domain is:
itanhaem.sp.gov.br
I ran this command:
certbot certonly --standalone -d www.itanhaem.sp.gov.br
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Cert is due for renewal, auto-renewing...
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for www.itanhaem.sp.gov.br
Waiting for verification...
Challenge failed for domain www.itanhaem.sp.gov.br
http-01 challenge for www.itanhaem.sp.gov.br
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
The following errors were reported by the server:
Domain: www.itanhaem.sp.gov.br
Type: dns
Detail: DNS problem: query timed out looking up A for
www.itanhaem.sp.gov.br; DNS problem: SERVFAIL looking up AAAA for
www.itanhaem.sp.gov.br - the domain's nameservers may be
malfunctioning
The problem seems to be within CloudFlare.
But only when being queried from certain IP networks.
A bit unusual for CloudFlare; But, no less, a show stopper for you.
Let's wait for some LE folks to get in and review this problem - @lestaff
I'm not sure the request would be made to those servers for the "www", but it is an interesting reply none-the-less.
Those servers should have returned the list of authoritative nameservers instead.
Like with [without "www"]: nslookup -q=a itanhaem.sp.gov.br dns4e.sp.gov.br.
Some information about me and the domain . I manage the website of Itanhaém City Hall (a small town in Brazil on the Atlantic coast Itanhaém - Wikipedia).
In Brazil, government domains follow a pattern. Like www.city.state.gov.br.
Prodesp(https://www.dominio.sp.gov.br) is the dns registrar responsible for the .sp.gov.br domains. Does not support dnssec.