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

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. If you are okay with this downside, or simply cannot use Nelify DNS for some reason, here’s how to do it!

1. Successfully Deploy the Branch to Netlify.

First, please make certain the branch has deployed successfully - meaning both the build and deploy must happen successfully, on Netlify.

If branch deploys are disabled or if the build/deploy processes are failing, then please resolve those issues before proceeding. If you run into any issues the following documentation may be helpful:

You might ask: Why do I need to deploy before configuring DNS in step two?

The answer is that the branch DNS record needs to exist with us here at Netlify first. This is simply because it will need to be entered with the third-party DNS provider in step two.

2. Create the DNS record with your current DNS provider.

Next, you’ll need to create a DNS record at your DNS provider pointing to the branch DNS record at Netlify.

Here is an example scenario:

  • the custom domain is www.example.com
  • the branch name is branchname
  • the branch should be served at https://branchname.www.example.com/
  • the TTL value (time to live value - more below) will be 3600 seconds which is one hour
  • the sub-domain at Netlify is happy-scientist-123456 (meaning the Netlify URL for the master branch is https://happy-scientist-123456.netlify.app/)

With the values above defined for this example, the DNS record you create would look like so:

branchname.www 3600 IN CNAME branchname--happy-scientist-123456.netlify.app.

The format above is required and no other naming conventions will work. The key points for the DNS record are:

  • There should be two dashes between branchname and happy-scientist-123456.
  • The record should be the type CNAME.
  • The branch name must match the sub-domain you want exactly. If your branch is called staging your sub-domain cannot be stage.www.example.com. It must be staging.www.example.com.

3. Confirm the new URL is working and, if so, contact support for SSL provisioning.

Yay! We’re done. Well, almost.

I did mention something before about missing out on “getting an SSL certificate configured automatically”.

Not to worry. Our technical support will be able to assist with that, but, before support can provision an updated SSL certificate, we need to confirm the domain name is working. (If it isn’t working the provisioning will fail so this must be completed first.)

So, how do you test if the DNS record is working correctly?

Well, if you are comfortable working in a terminal (aka, command line, shell, etc) the nslookup command (or dig) can confirm the DNS record is working correctly. Using this imaginary example above (with the branch server at branchname.www.example.com), the output of nslookup would look similar to this:

$ nslookup branchname.www.example.com

Non-authoritative answer:
branchname.www.example.com	canonical name = branchname--happy-scientist-123456.netlify.com.
Name:	branchname--happy-scientist-123456.netlify.com

Wonderful! We needed to confirm that branchname.www.example.com points to branchname--happy-scientist-123456.netlify.com and it does!

And remember that pesky TTL (time to live) value I mentioned previously? Here is why it matters.

DNS is recursive, meaning that if one DNS server doesn’t know an answer it asks others in a hierarchy. To prevent heavy traffic on the DNS servers at the top of the hierarchy caching is used. Instead of asking for the same DNS record over and over each time you visit the same domain name, both web browsers and intermediary DNS servers will cache the value for a certain time - the TTL value. The TTL value is the time (in seconds) that the record can/should be cached.

This matters because, if you are changing an existing record for domain (or, like me, you sometimes make a mistake when configuring your DNS records), we must wait for the old/incorrect DNS record to timeout before the new one will take effect.

On the other hand, if this is a new DNS record (meaning it is a newly added sub-domain which didn’t already exist) the TTL value won’t affect anything. This is because a new record, by definition, isn’t cached anywhere.

4. Contact Netlify Technical Support to get the SSL certificate extended to the new sub-domain.

If the nslookup test above succeeded, then the last step is to please contact our Technical Support team asking for the the SSL certificate to include the new branch sub-domain. You can do this by making a new topic in the community #Netlify-support category (or if you have a Pro plan or above, using our support form.)

This is the reason we ask you to confirm the new DNS record is pointing to the branch in step three. We cannot extend an SSL certificate to cover the new sub-domain until there is a DNS record pointing to Netlify.

Once the DNS record is configured, we will be happy to extend the SSL certificate to include the newly added branch sub-domain.

If there are questions about this, please let us know.

Custom subdomain for branch deploy
Creating a subdomain using Netlify DNS
Branch Subdomain and SSL Certificate
Configuring branch subdomain names
Adding new custom branch domain to SSL Certificate
Could you activate the https on my staging domain?
How to set up a staging site
Branch Deploys & Branch Subdomains on Custom Domain - nslookup fails "server can't find..."
Subdomain SSL Extension for Branch Deploy
Issue with staging subdomain propogating SSL
Branch Deploy SSL certificate extension
Certificate request
Subdomains with www on netlify - how to set up?
Subdomains with www on netlify - how to set up?
Point branch deploy to subdomain on Route53
Point branch deploy to subdomain on Route53
Issues with DNS settings from custom domain
SSL not deploying for branch subdomain
SSL certificate to include the new branch sub-domain for develop
Branch Domain SSL for Akita Software Staging
Branch Domain SSL for Akita Software Staging
SSL Let's Encrypt subdomain issue
Can you deploy existing build to another site?
Wildcard SSL certificate for subdomains (branch subdomains)
Provision SSL certification in anticipation of Netlify Transition
SSL certificate for Branch subdomain - 2473e964.netlify.app
Enable branch subdomains
Enable branch subdomains
Branch Subdomains not working correctly
Https certificate installation for subdomain
SSL certificate change for branch deploy
SSL Cert for branch deployment
Custom subdomain not resolving on branch deploy
Branch Deploy Periodically Failing [Likely Due to SSL Errors]
SSL Certificate for branch subdomain
NetlifyDNS - branch subdomain cert error
Enabling branch deploys for a site that doesn't use netlify DNS
SSL certificate for branch deploy
SSL certificate for branch deployment
Preview Builds on Custom Domains
SSL Certs for custom subdomain
Extend SSL certificate to branch subdomain - new
Request to extend SSL to new sub-domain
Assistance setting up SSL for branch deploy
Extend SSL certificate to branch subdomain
SSL on <branch>.<subdomain>.domain.dev
Branch Subdomain and SSL Certificate
Netlify, Branches & Bitbucket
Let's Encrypt certificate doesn't include branch subdomains after changing the primary domain
Branch Subdomain and SSL Certificate
Let's Encrypt certificate doesn't include branch subdomains after changing the primary domain
Deploying site on branch without build command
Is there a way to change the URL of deploy-preview?
Let's Encrypt certificate doesn't include branch subdomains after changing the primary domain
SSL certificate extension to the new sub-domain
Set up SSL for my branch deploy please!
Subdomain SSL Extension for Branch Deploy
We need to enable *.sta91ng.freshping.io for https://app-freshping-staging.netlify.com
Enabling SSL on Subdomains
404 Not Found error when accessing branch via CNAME
Branch feature SSL
Using one domain per branch
Is it possible to use SSL certificates with branch deploys, without Netlify DNS, while on the free plan?
Enabling SSL on Subdomains
Subdomain SSL for branch deploy
Help with SSL for Branch Deploy
Branch Deploy SSL Certificate
Request for SSL cert for staging branch deploy using external DNS
Subdomaine for branch
Extend SSL certificate to custom branch subdomain
Possile add same 404 error page for every subdomains?
Branch deploys not working when _not_ using Netlify DNS
I'm having issues deploying a branch to a subdomain
Add subdomain to SSL Cert
Request for SSL certificate for non-Netlify DNS branch deploy
Extend SSL certificate to new sub-domain
Branch Deploy SSL Cert
Request for SSL Certificate extension for branch deploy for non-netlify managed DNS subdomain
Certificate extension request
Request for SSL Certificate extension for branch deploy for non-netlify managed DNS subdomain
Extend SSL certificate for subdomain
I need to get SSL certs for our stanging branches
[Support Guide] DNS Quick Start - How to set up DNS