Score:0

Certificate validation issue with subdomains of subdomains

cn flag

I have a current, production certificate with a wildcard common-name hosted in Amazon Certificate Manager (ACM). I've added a CNAME with a subdomain of a subdomain (like ....) to our Route53 zone that points to our load-balancer (ALB). However, Chrome complains with

[SSL_ERROR_BAD_CERT_DOMAIN] "The certificate is only valid for *..." (domain intentionally sanitized).

What could the problem be? Am I wrong in assuming that wildcard certificates should handle any subdomain at all depths?

cn flag
Duplicate of: https://stackoverflow.com/a/9743652/706421
us flag
Rob
In short - the `*` wildcard only matches 1 subdomain level - see also https://serverfault.com/a/310545/960939
Patrick Mevzek avatar
cn flag
"Am I wrong in assuming that wildcard certificates should handle any subdomain at all depths?" Yes, you are wrong on this.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.