Provision SSL certification in anticipation of Netlify Transition

[luke]

Hi, @shogun_enterprises, automatic SSL for branch subdomains only works if the custom domain is using Netlify DNS.

This custom domain (shogun.cool) is not using Netlify DNS:

$ whois shogun.cool | grep "Name Server"
Name Server: ns-1239.awsdns-26.org
Name Server: ns-41.awsdns-05.com
Name Server: ns-1917.awsdns-47.co.uk
Name Server: ns-682.awsdns-21.net
Name Server: NS-1239.AWSDNS-26.ORG
Name Server: NS-41.AWSDNS-05.COM
Name Server: NS-1917.AWSDNS-47.CO.UK
Name Server: NS-682.AWSDNS-21.NET

So the automatic SSL for branch subdomains won’t work for this domain and the following instructions apply instead:

[Support Guide] How to use Netlify’s branch deploy feature without Netlify DNS

Last reviewed by Netlify Support Staff: August 2023 So - you’ve discovered the concept of branch subdomains and want to use them! But you can’t use Netlify’s DNS Hosting? Never fear, there is a way to do this and this post will explain how in detail! Please note, however, that going this route means missing out on single click setup and all the goodness it includes - for example, getting an SSL certificate configured automatically. We also have Automatic Deploy Subdomains, which allows users …

The configuration you described above does work with Netlify DNS. However, for external DNS services there is a manual process for SSL (as details in the support guide above).

If you want to test our automatic SSL certificates for branch subdomains, Netlify DNS must be enabled first.

​Please let us know if there are other questions about this.