Hi, @shenwilly. The issue for your domain was due to time to live issues and the SSL is working now.
The issue for you, @Mauricio-Natacci, is different. The issue in this case is that you made a DNS zone for the subdomain meetings.real-dev.com here:
https://app.netlify.com/account/dns/meetings.real-dev.com
However, when I check your domain’s configuration, you have delegated the apex to Netlify (meaning real-dev.com) , not just the meetings subdomain. This means the domain is currently misconfigured.
The steps to fix it are:
- At the registrar (which is https://www.namesrs.com/), revert back to using their default name servers.
- Once their name servers are working for this domain again add (do not replace the existing records, add these to the existing ones) the DNS records below at the registrar:
meetings.real-dev.com. 3600 IN NS dns1.p08.nsone.net.
meetings.real-dev.com. 3600 IN NS dns2.p08.nsone.net.
meetings.real-dev.com. 3600 IN NS dns3.p08.nsone.net.
meetings.real-dev.com. 3600 IN NS dns4.p08.nsone.net.
Note, the TTL values on the current NS records for the apex are 172800 seconds. This means it may be 48 hours before the these changes are detected by downstream DNS resolvers.
- After waiting 48 hours from the time the changes above are made, click the “Verify DNS configuration” button on this page below:
https://app.netlify.com/sites/meetings-management/domain-management#ssl-tls-certificate
The SSL provisioning will succeed if those steps are taken. You may not need to wait 48 hours but it is possible and that is the longest you would need to wait for the TTL to expire. However, if those instructions don’t work as promised, please let us know.