Custom domain and sub-domain setup errors that can be encountered when setting up your Link Settings page.
Modified on: Fri, Apr 6, 2018 at 2:03 PM
Custom root domain NS records not setup.
This means that your root domain is not setup with the correct NS records.
In your console, run $ dig NS [YOUR DOMAIN], i.e.: dig NS branch.app.link
Verify the NS records:
If they do not match the Link Settings page - please setup your domain’s DNS records with the correct NS records that are listed in the Link Settings page, and allow up to an hour for the change to propagate.
If the records match, and it has been over an hour since they were updated - please reach out to firstname.lastname@example.org, or your assigned TAM/SE.
I set up a custom domain for my links, but now all the content on that domain is gone.
Branch completely takes over the ownership of whichever domain is setup as a link domain in the Link Settings page. All the data that used to be available on that domain will no longer be available.
Disable the domain in Link Settings, and reset the NS records.
Either setup a different root domain, or setup a sub-domain with Branch, i.e. link.branch.io
My sub-domain is not properly configured with a CNAME.
For custom sub-domains Branch requires a CNAME record to be created, in the DNS records of the sub-domain, which points to custom.bnc.lt.
In your console, run $ dig CNAME [YOUR SUB-DOMAIN], i.e.: dig CNAME branch.app.link
Verify the CNAME record:
If the CNAME record is not setup - please add a CNAME record pointing to custom.bnc.lt, and try setting up your custom domain again. Make sure to refresh the Link Settings page once you are done, and verify that the error is not shown any more.
If the CNAME record is set up for custom.bnc.lt, but the error is still displayed - please reach out to email@example.com or your assigned TAM/SE
Did you find it helpful?Send feedback