Please review the documentation and requirements for uploading wildcard certificates to SolarWinds Service Desk:
https://support.solarwinds.com/SuccessCenter/s/article/ITSM-Uploading-a-Wildcard-SSL-Certificate-to-SolarWinds-Service-Desk?language=en_US
We could not implement a wildcard certificate due to the restrictions in place per RFC 1034 s3.6.2 (updated by RFC 2181 s10.1), which prevents our DNS provider from allowing the addition of a TXT record when a CNAME record is present.
Alternatively, we could add an A-record, provided the IP defined doesn't change, which would allow for the creation of the requisite TXT-record.
Another alternative could be the use of a sub-domain for the TXT record. We could add a TXT record to "<GUID>.domainkey.<custom_domain>", which would allow customers to align with the RFC requirements and would mirror the domain verification methods used by Google, AWS, and other providers.
