As part of your Bynder contract, you have the ability to configure a custom URL. This configuration is completely optional. Your portal will be activated with a standard default Bynder URL in the format of xyz.bynder.com. All of the links related to your portal will use your Bynder portal URL. You can customize this URL to have a more consistent brand experience with other tools you use or websites you own.
All domains hosted on Bynder require a valid SSL certificate. We supply a default URL and SSL certificate by default. To use a custom domain, request a valid SSL certificate. The certificates available in Bynder do not expire, so there is no need to worry about renewal or potential downtime. AWS Certificate Manager (ACM) automatically renews these certificates.
Note
- The Requested URL needs to be a sub-domain.
I Want a Custom URL and Need to Request an SSL Certificate
You can request an SSL certificate yourself using our automatic procedure. Please contact your customer success manager or onboarding manager if this does not work for your portal.
Automatic Procedure
-
Navigate to your Portal.
-
Select Portal settings> Domain Management, located on the left sidebar.
Note
You can't use the automatic procedure if the SSL page doesn't load and only shows the "Get a personalized URL for your Bynder portal." message.
Use the manual procedure instead.
-
Select the Request SSL certificate button.
(Please confirm the warning with Yes, and request an SSL certificate if you already have a custom URL and want to add a new one). -
Enter the custom URL you want to use in the text field.
-
(Optional) Click the + Add domain button to add other custom URLs.
Note
You can request a maximum of 15 domains.
-
Click Send request to submit the custom URL(s). The DNS CNAME records will be generated, which can take up to 15 minutes.
-
Go to the DNS CNAME records section and copy the Name and Value values of both CNAMEs.
-
Send the two CNAME records to your IT department or the party that manages the custom domain and ask them to add both records to the domain setup. Make sure your team is aware of the following:
- Some domain providers implicitly add the domain name at the end of CNAME entries. Please check if this is the case for yours. If so, you must exclude your domain name when adding the CNAME records.
- Bynder cannot support APEX records as you cannot add a CNAME
-
The DNS records must be added to their domain setup within three days. After 72 hours, the records will expire, and new records must be requested.
-
The leading underscores (_) for the second CNAME record must be included when adding the values to the domain setup.
-
Some domain providers automatically populate the name when you add the Name value (for example, byndair.com).
-
In that case, only the subdomain must be entered in our example, byndair. If you enter the entire domain, it will result in a faulty record. For example:
assets.byndair.com.byndair.com
. -
It's advised to set the TTL (time to live) setting of the new CNAME records to 5 minutes (300 seconds) to validate them as quickly as possible.
-
Ask your team to inform you once they've added the records to their domain setup.
-
Bynder will try to validate the records automatically. How long this takes depends on the domain's TTL (time to live) setting. You can follow the status on the SSL page. The status for each domain is also graphically indicated. Click the Refresh request button. This will reactivate the records and give you another 72 hours to add them to the domain setup. The records will remain the same.
The validation has failed.
The validation is in progress.
The validation is successful.
Configuring Primary Domain and the Redirects.
Once the domain has been validated, you can start configuring the primary domain and the redirects.
-
Navigate to the Primary domain, redirects section on the Domain management page, and click the Edit button.
-
Select the primary domain for the portal and click Next.
-
Select the other domains that should redirect to your primary domain. The selection consists of all the domains set up for the portal, including the original (get)bynder.com URL.
-
Click Save Changes to save the primary domain and the redirects.
-
Inform your domain manager that they shouldn't delete the CNAME records after validation.
-
The CNAME records must remain available for the custom URL(s) to continue working and for the SSL certificate to renew automatically.
Manual Procedure
If the automatic procedure doesn't work for your portal, you can follow the steps below to request a custom URL.
- If you are in the implementation phase, please reach out to your Onboarding Manager.
- If the portal is already live and you want to change it, please contact your Customer Success Manager.
- Provide them with the primary domain(s) or subdomain(s) for which an SSL certificate needs to be requested.
- (Optional) Let us know if you want a redirect in place that will redirect your old DAM URL(s) to your new Bynder portal URL. For example, if you want the original (get)bynder.com URL to redirect to your new custom URL.
- We will provide you with two DNS records per domain that must be added on your side. One CNAME record verifies that the domain name is yours and authorizes AWS to request or renew the SSL certificate on your behalf. The other record redirects the domain name to the correct server. Read more about adding DNS records here.
- Bynder will automatically try validating the added CNAME records. We'll let you know once the domain is fully validated, and you can use your custom URL.
Note
Please don't remove the CNAME records after validating the custom URL. The records must remain available for the custom URL to continue working and for the SSL certificate to renew automatically.
I Need to Renew an Existing SSL Certificate
-
Please contact our Support team and tell them the primary domain or subdomain for which the SSL certificate needs to be renewed.
-
We will give you two DNS records that need to be added.
-
One CNAME record verifies that the domain name is yours and authorizes AWS to request or renew the SSL certificate on your behalf.
-
The other record redirects the domain name to the correct server. Read more about adding DNS records here.
-
How to Add DNS Records
The Domain Name System (DNS) database helps find and convert Internet domain names into Internet protocol (IP) addresses. Please add a DNS record for the custom URL to redirect to your Bynder portal.
How to Add the DNS Records?
You can add the DNS records to your domain provider's configuration panel. For more information, check your domain provider's help center.
You can find instructions on adding a CNAME for most common domain registrars below:
-
Obtain the needed CNAME records following the instructions in the I Want a Custom URL and Need to Request an SSL Certificate section. The two sets of records follow the below format.
example.bynder.com CNAME rr-example.bynder.com
This record tells the browser that example.bynder.com should look for the data in rr-example.bynder.com.
"Name":"_58d7b754aa7ca067fc00daa3b7agc019.customURL.bynder.com, "Type": "CNAME", "Value": "_7c5cb951ded42e9r9e7fse2a96as10d0.wggjkglgrm.acm-validations.aws."
-
Configure the DNS records for your domain. Ensure the record type is CNAME and the pattern is <Record1> POINTS TO <Record2>.
-
Set the TTL to 300 seconds (5 minutes). If you are not familiar with TTL, read more about it here.
-
Repeat the above steps to add the second record.
-
Once your DNS records are in place, follow the steps below to verify that they have been added correctly.
Verification
-
Go to https://toolbox.googleapps.com/apps/dig/#CNAME/ and enter your custom URL.
-
Check the ANSWER SECTION, which should look like the example below.
example.bynder.com IN CNAME rr-example.bynder.com. global.bynder.com. 300 IN CNAME re-eu-central-1.bynder.com.re-eu-central-1.bynder.com. 60 IN A 52.29.108.244 re-eu-central-1.bynder.com. 60 IN A 52.59.57.197
If the dig output is unexpected, verify the records have been added correctly. For more information, check the Troubleshooting section below.
Troubleshooting
DNS Lookup
Use MxToolbox to check if the DNS records have been correctly added to your domain setup.
Implicit Domains
This issue commonly occurs with providers such as GoDaddy, Cloudflare
You may experience issues related to implicit domains when verifying your DNS records. For example, if your hosted domain is *.bynder.com and you want the custom URL to be media.bynder.com
We'll provide you with the following records:
media.bynder.com CNAME rr-media-bynder-com.bynder.com "Name": "_58d7b754aa7ca067fc00daa3b7agc019.media.bynder.com, "Type": "CNAME", "Value": "_7c5cb951ded42e9r9e7fse2a96as10d0.wggjkglgrm.acm-validations.aws."
After adding these records, they won't be verified, which is caused by bynder.com already being appended to any record you add. Even though you added media.bynder.com as a record, the implicit domain causes you to add media.bynder.com.getbynder.com. Follow the steps below to fix this.
-
Verify if the issue is caused by implicit domains by checking the record on https://toolbox.googleapps.com/apps/dig/#CNAME/
;; ANSWER SECTION: media.bynder.com.bynder.com IN CNAME rr-media-bynder-com.getbynder.com global.getbynder.com. 300 IN CNAME re-eu- central-1.getbynder.com. re-eu-central-1.getbynder.com. 60 IN A 52.29.108.244 re-eu-central-1.getbynder.com. 60 IN A 52.59.57.197
The above example shows that the appended URL points to the correct record.
-
Remove the implicit domain from the records being sent.
media CNAME rr-media-bynder-com.getbynder.com. <—.bynder.com is removed here And "Name": "_58d7b754aa7ca067fc00daa3b7agc019.media . <—.bynder.com is removed here "Type": "CNAME", "Value": "_7c5cb951ded42e9r9e7fse2a96as10d0.wggjkglgrm.acm-validations.aws."
-
Apply the modified records to your DNS setup.
-
Contact your domain provider's technical support department to help with issues.
FAQ
Can I provide my own SSL certificate?
No, this is not possible. We want to protect you from expiring certificates or potential downtime. That is why we'll request an SSL certificate for you and ensure it will be renewed automatically using AWS Certificate Manager (ACM).
Can I have multiple custom URLs for my Bynder portal?
Yes, this is possible. You can request multiple custom URLs for your Bynder portal and redirect all of them to your primary Bynder portal URL.
What should I do when I can't add the provided CNAME records?
Contact your domain provider's support department and ask for further technical assistance.
Some providers don't support adding a CNAME starting with an underscore (_) via their admin panel. You can ask their support agents to enter the record for you via the backend of their system.
Why is my SSL certificate not validating while the records have been added correctly?
Please see our Troubleshooting section for some troubleshooting steps and check whether your records have been added correctly by looking them up here.
Some providers offerthen option to use a proxy to mask your records. If this is the case, AWS can't verify the record. If the validation takes over 72 hours, please turn off the proxy settings and ask your CSM to help verify.
Updated