We recently migrated our web app (static files) to Netlify whilst simultaneously keeping our old site up & running, allowing us to migrate our clients carefully & gracefully.
- Our old site domain is: https://cloud.quill-interactive.co.uk
- In Netlify, we created a domain alias of cloudv2.quill-interactive.co.uk + a lets encrypt cert
- We then implemented a feature switch and some redirects in our backend so that when a migrated client hit “cloud” they were redirected to “cloudv2” - which all works ok.
Now we have successfully migrated all our clients, our new goal is to ditch the feature switch code/redirects, make our original “cloud” subdomain to point directly at Netlify, and retire the cloudv2 sub domain. This is what we’ve done so far:
We added the domain alias “cloud.quill-interactive.co.uk” to Netlify, which currently shows a status of “check DNS config”.
Before we can change the DNS to a CNAME record aimed at Netlify, we need to ensure the SSL cert in Netlify supports this new subdomain.
But hitting “Renew Certificate” on our let’s encrypt cert, does nothing. It doesn’t throw an error but it doesn’t renew to include our new domain alias. We guess because of its “check DNS config” status.
So it appears that we cannot update our let’s encrypt cert until we update our “cloud” DNS record and vice versa! Catch 22?
How can we get ourselves out of this loop?
Any help much appreciated.