Wildcard DNS => SSL certificate not valid?

Support
1

I configured a CNAME DNS entry “*.typebot.io” that points to “bot.typebot.io” where I have a Firebase project hosted.
But when I navigate to a custom subdomain I get the NET::ERR_CERT_COMMON_NAME_INVALID error.

The Let’s encrypt certificate generated by Netlify seems to sign “*.typebot.io”. Am I not understanding something?

2

Hi, @baptisteArnaud. Wildcard subdomains aren’t enabled by default and can only be enabled from our end. There are also a few requirements before we’re able to do so:

  • Either you have to use Netlify DNS so we can get you a wildcard SSL cert, or you must bring a custom wildcard certificate.
  • We can only do this for a site that’s on a paid team (see Netlify Pricing and Plans for details)

Also note:

You can’t use domain aliases on the site with Wildcard subdomains enabled, just the bare domain and subdomains under your primary domain. If you try to add a domain alias then it won’t work.
The primary custom domain for the site, if it is a example.com with www.example.com setting in our UI, must be www.example.com and not example.com!

Once the wildcard subdomain feature is enabled, you do not need to add new subdomains under the site settings. You’ll will need still need to create DNS records.

This might be a single wildcard DNS record for all subdomains (like a CNAME for *.example.com pointing to the netlify.app subdomain for the site). Alternatively, you can also create the individual DNS records to add each subdomain (like CNAMEs for subdomain-a.example.com, subdomain-b.example.com, etc.) as covered in our external DNS documentation. Both work so please do whichever you prefer.

The only requirement not met at this time is the paid team type (Pro or higher). Once that change is made the feature can be enabled for this site.

If there are other questions or concerns, please let us know.