We have two existing a-records named sealifebase.ca and sealifebase.se for our domain sealifebase.org. Sealifebase.ca has its own SSL certificate named sealifebase.ca while the other one has none. When accessing through sealifebase.org an error that states NET::ERR_CERT_COMMON_NAME_INVALID usually appears. What can be done to solve this issue?