- Knowledge Base
- System
- Get a Personalized URL for your Bynder Portal (Custom URL)
Get a Personalized URL for your Bynder Portal (Custom URL)
During the onboarding process Bynder sets up a portal for you. The default portal URL ends in (get)bynder.com. If you want your portal URL to align more with your branding you may want to use a custom URL. For example, media.yourdomainname.com.
Every domain we host on Bynder requires a valid SSL certificate. By default, we provide you with a default URL and SSL certificate. If you want to have a custom domain we need to request an individual valid SSL certificate for you. Certificates normally expire after a certain amount of time, but with the certificates we provide you no longer have to worry about expiration dates or potential down time. We'll request a SSL certificate for you and make sure that it will be renewed automatically using AWS Certificate Manager (ACM).
Read more about the process of setting up a custom URL below.
When you're still in the implementation phase, please contact your Onboarding Manager. Please reach out to your Customer Success Manager if the portal is already live.
Provide them with the primary domain(s) or subdomain(s) for which a 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 need to be added on your side. One CNAME record is used for verifying that the domain name is truly yours and to authorize AWS to request or renew the SSL certificate on your behalf. The other record is used to redirect the domain name to the right server. Read more about adding DNS records here.
Bynder will automatically try validating the added CNAME records. How long this takes depends on the TTL (time to live) setting in your domain management. We'll inform you once the domain is fully validated and you can start using your custom URL.
Note
Do not remove the CNAME records after the custom URL has been validated. The records have to remain available in order for the custom URL to continue working and for the SSL certificate to renew automatically.
Reach out to our Support department and provide them with the primary domain or subdomain for which the SSL certificate needs to be renewed.
We will provide you with two DNS records that need to be added on your side. One CNAME record is used for verifying that the domain name is truly yours and to authorize AWS to request or renew the SSL certificate on your behalf. The other record is used to redirect the domain name to the right server. Read more about adding DNS records here.
In order for the custom URL to redirect to your Bynder portal we ask you to add DNS records on your side.Read more about DNS records and the setup below.
The domain name system (DNS) is a naming database which takes care of locating and translating internet domain into internet protocol (IP) addresses. The domain name system maps the name people use to locate a website to the IP address that a computer uses to locate a website/server. Read more about DNS here.
You can add the DNS records in the configuration panel of your domain provider. Check the help center of your domain provider for more information.
You can find instructions on adding a CNAME for most common domain registrars below:
Contact your Onboarding Manager or Customer Success Manager to receive the DNS records. We will provide you with two sets of records that 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. Make sure that record type is CNAME and that the pattern is <Record1> POINTS TO <Record2>.
Set the TTL to 300 seconds (5 minutes). Are you 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 verify if they have been added correctly by following the steps below.
Go to https://toolbox.googleapps.com/apps/dig/#CNAME/ and enter your custom URL. Quite some technical information will be returned.
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
Verify if the records have been added correctly if the dig output is not as expected. Check the Troubleshooting section below for more information.
Use MxToolbox to check if the DNS records have been added to your domain setup correctly.
This issue commonly occurs with providers such as: GoDaddy, Cloudflare
When verifying your DNS records you may experience the issue related to implicit domains. 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 that you actually added media.bynder.com.getbynder.com. Follow the steps below to fix this.
Verify if the issue is cause 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 is pointing to the right 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.
Reach out to the technical support department of your domain provider if you still run into issues.
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 a SSL certificate for you and make sure that 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 the support department of your domain provider 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?
Check our Troubleshooting section for some troubleshooting steps and check whether your records have been added correctly by looking them up here.
Some providers offer an option to use a proxy to mask your records. AWS can't verify the records if this is the case. If the validation takes more than 72 hours disable the proxy settings and ask your CSM to further assist you with the verification.