How To Create A Portal Custom URL

Summary

Bynder allows all portals to have and create custom portal URLs. 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.

Note: The requested URL must be a sub-domain. Bynder cannot support APEX records, but users could request www.yourdomainname.com. Keep in mind that to access the portal users will need to use the full URL including the ‘www’, otherwise it will not work.

Who?

This feature/solution is enabled by a Bynder Admin.

Don't have Bynder yet? Start Here.

The Bynder Admin must have the Manage Portal Settings permission enabled to create custom portal URLs.

Why?

Bynder understands brand consistency, and offers many solutions to empower users to enable customized brand experiences for their portal, including custom portal URLS. Custom portal URLs are an excellent way to maintain brand consistency while using Bynder. We even assist in the security of these custom links by requiring SSL certificates. All domains hosted on Bynder require a valid SSL certificate. We supply a default URL and SSL certificate. When using a custom domain, users must 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 must be a sub-domain.

How?

Automatic Procedure

Navigate to your Portal.
Select Portal settings> Domain Management, located on the left sidebar.
- If you do not see the Domain Management option in your portal, please contact Customer Support.
- 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. You will need to use the manual procedure.
Select the Request SSL certificate button. Confirm the warning with Yes, and request an SSL certificate.
Enter the custom URL you want to use in the text field.

Note: If you already have a Custom URL and are adding an additional domain, make sure to include the current URL in the request - otherwise the current URL will be replaced. (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, this 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 the 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.
- 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.

Note: If you want to remove your current primary domain, we strongly recommend requesting a new SSL that still includes that domain and afterwards set up redirection in your portal. Completely removing your current primary domain will break all your public links.

Note: It is not possible to add new domains if other domains are still pending validation. Please make sure to first validate domains from your last SSL request before requesting a new one.

Manual Procedure

If the automatic procedure isn't available for the portal, users 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 Customer Support.
Provide them with the 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.
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.

Configuring The 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.

Renewing 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.

Updating The Current Primary Domain

If your primary domain is a custom domain, you can update it yourself in Domain Management. Follow the steps outlined in the Automatic Procedure section.

Note: We strongly recommend requesting a new SSL that still includes the old primary domain and afterwards set up redirection in your portal. Completely removing your current primary domain from the SSL request will break all your public links. To set up a redirect, follow the steps outlined in Configuring The Primary Domain And The Redirects.

Note: If your users log in through SSO, updating your primary domain will require changes to your SSO configuration.

To avoid any downtime we recommend following below steps in the correct order:

Request new SSL with both the old and new primary domain.
Add CNAME1 to validate your new domains. Once your new CNAME1 record displays as in the Domain Management page
Update your SSO configuration.
- If users log in through SSO, updating the primary domain will require changes to the SSO configuration. If you are using the self-service SSO, it is possible to update this yourself with help of your IT department. Users will need to update the Service Provider Issuer and Assertion Consumer Service (ACS) URLs in the identity provider configuration to the new domain.
  
  For example, if these were the URLs:
  
  https://currentdomain.bynder.com/v7/idp/sso/saml/id/metadata
  
  https://currentdomain.bynder.com/v7/idp/sso/saml/id/acs
  
  They will need to be updated to:
  
  https://newdomain.bynder.com/v7/idp/sso/saml/id/metadata
  
  https://newdomain.bynder.com/v7/idp/sso/saml/id/acs
  
  Make sure that any group or profile mapping set up in the system is still relevant. Sometimes mapping names might correspond to the name of the old domain. Once completed, the SSO through the old URL will no longer work. Set up the redirection:
  - The redirection CNAME2 record must be added to the DNS records to set up the redirection.
  - The primary domain and all redirects are correctly set up within the Domain Management page
  Note: If your portal is on legacy SSO, please contact Support to help you with the necessary updates. Your IT department will need to be involved too.

Note: If your primary domain is a Bynder domain or if you don’t see the Domain Management section at all, please contact Support to help you.

How to Add the 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. You can add the DNS records to your domain provider's configuration panel.

You can find instructions on adding a CNAME for most the common domain registrars below:

GoDaddy

NameCheap

Netfirms

Obtain the needed CNAME records. 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

Implicit Domains

This issue commonly occurs with providers such as GoDaddy, and 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 here.

;; 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.

FAQs

Can I provide my own SSL certificate?

No, we'll request an SSL certificate for you and Bynder will ensure it is renewed automatically using AWS Certificate Manager (ACM).

Can I have multiple custom URLs for my Bynder portal?

Yes, you can request multiple custom URLs for your Bynder portal. Please note that the URLs will always redirect to the same Bynder portal. A custom URL does not create a new Bynder portal with different settings. The maximum amount of custom URL's is 15.

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.

Why is my SSL certificate not validating while the records have been added correctly?

Some providers offer the 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 Customer Support to help with verification.

Why is my SSL request pending even though I verified it successfully?

When creating a new SSL request, you will receive two CNAMEs. The first one is used for redirection (pointing visitors of the custom domain to Bynder portal) and the second one is used for verification. It is critical that both CNAMEs are added to the domain setup by your IT department. Often the redirection record is forgotten, which will cause the SSL request to stay in a pending state. It is also important that the DNS record is not removed after it has been validated. Removing the redirection CNAME from your domain setup will break the SSL and prevent users from being able to make any adjustments to it.

How can I change my Bynder subdomain?

To change your *.(get)bynder.com subdomain please contact Customer Support. If you have custom domains set up, Customer Support will need to delete all of them before the change of your Bynder subdomain can be processed. During the change the portal will experience about 10 minutes of downtime.

Note: All public links that were shared using the previous Bynder domain will no longer work. This includes all content embedded in Studio templates, CXUC guides, landing pages and homepage, as well as links to shared collections.

What if I cannot remove a domain because the invalidation record is missing?

If the option to remove the domain is not available, the admin can add the missing invalidated record to the DNS. Then, the option to delete it will show up.

I followed Updating The Current Primary Domain section including changes to SSO configuration, but SSO doesn't work/SSO button leads to the old domain?

Check that the IDP that is being used doesn't override the Host/X-Forwarded-Host headers. Additionally, if using a proxy, make sure the proxy is forwarding the X-Forwarded-Host header with the correct value for the new primary domain.

If I add an additional custom domain and update the redirect in the domain configuration page, but leave the old domain in place, will I need to update the SSO configuration?

Yes, users need to update SSO when updating the primary domain to the new domain.

How To Configure SAML, OpenID, And Google Single Sign-on (SSO)

Level: Expert

Expert-level articles are for users who have significant prior Bynder knowledge. These articles require you to know a lot of Bynder information and may also require higher-level portal rights to accomplish the task outlined within the article.

Updated May 15, 2026 14:06

How To Create A Portal Custom URL

Summary

Who?

Why?

How?

Automatic Procedure

Manual Procedure

Configuring The Primary Domain And The Redirects

Renewing An Existing SSL Certificate

Updating The Current Primary Domain

How to Add the DNS Records?

Troubleshooting

FAQs

Related Articles

Level: Expert

<%= previousTitle %>

<%= nextTitle %>

In this article

Categories

Toggle navigation menu

<%= category.name %>