Thanks! I didn’t realize that I could add status.amorrissound.com ; I thought it had to be a domain attached to my Netlify account.
If you could point to what led you to that conclusion - community article, docs, blog post, our app’s UI, etc - we’d love to see if we can improve it to be clearer!
Just out of curiosity, you mentioned “a few dozen separate names”, do you know the exact number? If there is a cap, is it possible to pay to increase it?
limit is 100, as that is the most our SSL provider can handle:
If you have a lot of subdomains, you may want to combine them into a single certificate, up to a limit of 100 Names per Certificate .
That limit is a hard limit.
We suggest no more than 50 names per site, PARTICULARLY if you are having customers configure DNS (e.g. yourproduct.theirdomain.com). You will have to provide a fair amount of tech support to those customers of yours around configuring this DNS appropriately - you’ll need to learn about
CAA dns records and how to identify ones that will impact us, for instance - so please be aware that this is a pattern other customers use, but that it does cause their teams some struggles to provide that tech support. We’ll be equally available to help you help them, of course, but it’s not going to be a very fast process with you proxying questions to us and us trying to debug the black box. The main customer I am thinking of who does this is now up to 4 separate but identical sites each with dozens of (different) theirproduct.customerdomain.com names on each site, so it is possible to scale this as far as you want to go - just a bit of a hassle.
A different pattern that some customers use with LESS hassle, is the pattern:
We have a feature that allows us to automatically serve *.yourdomain.com the same site WITHOUT particular configuration in the UI. It has a few limitations that I can talk through if you’re curious, namely in that your pattern has to match the *.somedomain.com rather than varying domains.