Currently the domain name of a certificate is identified by the CN. This is deprecated and can only use a single (sub-)domain. If a certificate contains several domains, TLSA records for all of them need to be created so the code has to be rewritten to use the SubjectAlternativeName instead and accommodate the case if there are more than one.
Currently the domain name of a certificate is identified by the CN. This is deprecated and can only use a single (sub-)domain. If a certificate contains several domains, TLSA records for all of them need to be created so the code has to be rewritten to use the SubjectAlternativeName instead and accommodate the case if there are more than one.
Helmut Pozimski
Currently the domain name of a certificate is identified by the CN. This is deprecated and can only use a single (sub-)domain. If a certificate contains several domains, TLSA records for all of them need to be created so the code has to be rewritten to use the SubjectAlternativeName instead and accommodate the case if there are more than one.