It looks like your SSL cert is for three specific domains as opposed to being for *.giessdenkiez.de and giessdenkiez.de- we usually automatically create the latter (with wildcard) for sites using Netlify DNS. We’re looking into why you have that kind of cert and will get back to you soon!
Ah, the problem is that while it looks like you’re using our DNS in our UI, you actually are not. Checking the name servers here shows that you’re using non-Netlify name servers:
Would it be possible for you to delegate your domain to Netlify at your registrar? Here are our docs for how to do that:
This would make the branch subdomain part a bit simpler.
If you’d rather keep your existing DNS hosting, you’ll want to create DNS records at your DNS host pointing to Netlify, and then delete the DNS zone in the Netlify UI. The branch subdomain part with externally hosted DNS is more manual, but still very possible!
Let us know your preference re: DNS hosting (Netlify’s or not-Netlify’s) and then we can get the branch subdomains sorted out.
I was trying to enable a branch subdomain preprod for my custom domain lume.com.ar (delegated to Netlify DNS) but it doesn’t seem to work as far as I keep getting an ERR_NAME_NOT_RESOLVED when trying to access preprod.lume.com.ar
My deploy context preprod is working great, and Netlify recognised it at once when setting it as branch subdomain. SSL cert also looks good with a wildcard before the domain (*.lume.com.ar), but just in case, I renewed it after adding the subdomain modification.
I don’t know if it takes some time to update in order to see it live, or even if I’m missing something. Do you have any idea what’s going on?
That error was a DNS problem, not SSL, and a bit hard to diagnose in retrospect (once DNS changes, there is no historical record of what it used to be), but I am very glad to hear it resolved so quickly for you, since upon investigation I found it to be optimally configured and working well