SniCertificate::CertificateNonvalidError: Unable to verify challenge for www.ios.dz: DNS problem: query timed out looking up A for www.ios.dz; DNS problem: query timed out looking up AAAA for www.ios.dz
the website is runing from many month without no problem in netlify but this week i receive an error for certificate SSL. i do not change anything in my dns server.
As far as I can tell, your A record is misconfigured:
% host ios.dz
ios.dz has address 104.198.14.52
Could you please change the A record to point to Netlify’s load balancer IP 75.2.60.5 ? Once propagation takes place, Let’s Encrypt should be able to renew the cert.
can you please trigger regeneration of let’s Encrypt certificate because i don’t have the possibility to do it from my side. i think DNS propagation is done from 17hours earlier
Your site has reached Let’s Encrypt’s rate limit. It should lift in about a week’s time before we can try renewing your cert again.
Apologies, I didn’t notice this earlier but it seems you’ve configured a DNS CAA record on that domain that blocks us (and everyone else, as far as I can tell) from issuing SSL certificates for every hostname under the ios.dz domain. This is the record in question:
% host -t caa ios.dz
ios.dz has CAA record 0 issuewild "letsencrypt.org"
While I can’t advise you on your own security policies, your IT and/or security team probably put that in place and you should talk with them about the effects of it on the sites you host with us. We will not be able to obtain or renew any SSL certificates for that domain until you change the setting in some way, so you’ll have to generate and bring your own custom certificates if you want to use our service and leave that record in place.
You can of course change it or narrow its scope to achieve similar unblocking, but again that is a policy decision your team will need to make.
Something further seems to be wrong with your DNS. I can see you host it yourself, so hopefully you are savvy to fix it. This 3rd-party testing tool shows the problems:
Specifically, you will need to fix at least the red “errors” before DNS will work for everyone - including Netlify + Let’s Encrypt, as well as your site visitors, people who want to email you, etc.
