I see this issue is a fairly common one and I have perused other similar questions. Sorry for reposting, it just seems to have quite variable solutions.
My site is colinr.tech.
I am configuring it using external DNS as I am pulling the data from a WordPress installation on the subdomain at another hosting provider.
wp.colinr.tech
It was all working up until late this week and I can’t figure out where it is going wrong. These are my domain settings for this site at Netlify. I am pointing the A record which is set at my hosting provider.
Hi, @0x0Bop. It appears that you have a Netlify DNS zone for this custom domain here:
However, the DNS zone is inactive and that will prevent us from being able to create or update SSL certificates for this custom domain.
There is more information about how to detect and fix this type of issue in this support guide:
Would you please read the support guide above and try one of the two solutions described there?
If this doesn’t fix the issue, please let us know what steps you tried and what the result was. We will be happy to research what is happening and suggest steps to resolve it.
Thanks for all the information it was a really useful guide.
I went with Solution #1: Delete the inactive DNS zone and use external DNS. I have configured a CNAME record on my hosting provider DNS to point to colinr-tech.netlify.app.
I thought I had configured it this way to start with but I must have messed something up.
The site is still accessible, I’m just waiting to see if the SSL resolves.
At this point I am wondering about trying out solution 2. But before I do, I was wondering if it might be worth trying to redirect one of the records shown above.
From what I can gather letsencrypt is still finding this particular inactive DNS @ netlify.
Hi, @0x0Bop. Actually, this time it did do the HTTP-based verification. However, there is an AAAA record for the apex domain which doesn’t point to Netlify:
colinr.tech. 3600 IN AAAA 2a07:7800::135
Let’s Encrypted queried this IP address for the HTTP-based verification and, again - because this isn’t an IP address at Netlify, the HTTP verification. If you delete that record above, the “Renew certificate” button should work in, at most, the next hour. (I say one hour because the TTL value in the record is 3600 seconds).
If it still doesn’t work once the AAAA record is deleted, please let us know.