--- schema_version: "1" id: c511056ede888e25d79ee29dd7e9b7a35134968effbb9f69173e4dfbc55191fe title: Configure Wildcard Custom Hostnames collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_add_wildcard_custom_hostname.md canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_add_wildcard_custom_hostname.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: dd7d81d53972394aab34a5f75f9ea8744d84247a1a6d3fc75987cd4ffa8b0111 description: Use a single wildcard custom hostname (for example, *.merchantsite.com) to cover multiple subdomains and reduce onboarding and management overhead in B2C Commerce eCDN via Business Manager. products: - Commerce - B2C Commerce release: "264" --- # Configure Wildcard Custom Hostnames Use a single wildcard custom hostname (for example, `*.merchantsite.com`) to cover multiple subdomains and reduce onboarding and management overhead in B2C Commerce eCDN via Business Manager. A wildcard custom hostname such as `*.merchantsite.com` automatically covers multiple subdomains like `shop.merchantsite.com` and `blog.merchantsite.com`. Because you don't configure each subdomain individually, wildcard hostnames significantly reduce the overhead of onboarding and managing new hostnames. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_important.png) Important A specific-hostname certificate takes precedence over a wildcard certificate. Create a specific-hostname certificate (for example, `shop.merchant.com`) even if a wildcard certificate (`*.merchant.com`) already exists. When both are present, the specific-hostname certificate takes precedence per established hostname priority rules. Wildcard Custom Hostname Requirements | Requirement | Details | | --- | --- | | Zone Type | Wildcard custom hostnames are only supported for **Proxy V2** zones. | | Unique hostname across instances | Only one instance of a specific wildcard custom hostname is allowed across all e-commerce instances (for example, development, staging, production). If you use `*.merchantsite.com` in production, use a different hostname like `*.dev-merchantsite.com` or `*.stg-merchantsite.com` for other instances to avoid conflicts. | | Certificates | Customers can choose between **eCDN Managed Certificate** (handled and renewed by eCDN, reducing overhead) or **Self-Managed Certificate** (customers upload their own certificate). | | SAN coverage (self-managed) | For self-managed certificates, Subject Alternative Names (SANs) cover both the wildcard hostname (for example, `*.merchantsite.com`) and the root domain (for example, `merchantsite.com`). Failure to cover both results in an error during upload in the Business Manager (BM) UI. | | SAN coverage (eCDN managed) | For eCDN managed certificates, SAN values automatically include both the wildcard and root domain. | | Legacy/O2O conflict | If a customer already has an active legacy zone (via eCDN or as an existing Cloudflare customer/O2O) for the fully qualified domain name (FQDN) (for example, `merchantsite.com`), the legacy zone takes priority over the Proxy zone. In this scenario, wildcard custom hostnames do not work. See [Hostname priority](https://developers.cloudflare.com/ssl/reference/certificate-and-hostname-priority/#hostname-priority). | | Certificate validation method | When using eCDN managed certificates for wildcard hostnames, certificate validation uses the **TXT** method. Activating the certificate requires adding the necessary CNAME/TXT DNS records to your authoritative DNS. | 1. Make sure that your aliases include all hostnames associated with the domain. ![Configure aliases to include all hostnames associated with the domain.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_ecdn_config_wildcard_hostname_1.png) 2. After you configure the proxy zone and it's active, verify that all hostnames added to the alias file appear on the eCDN settings page. ![Verify hostnames appear with eCDN settings.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_ecdn_config_wildcard_hostname_2.png) 3. Select **Settings/Certificates** next to the proxy zone to open the SSL configuration window. ![Upload Custom Certificate dialog with eCDN Managed Certificate selected and Enable Wildcard Hostname highlighted](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_ecdn_config_wildcard_hostname_3.png) 4. Select **Add Certificate** to open the certificate dialog and locate the **Enable Wildcard Hostname** toggle. ![Upload Custom Certificate dialog with TXT Validation and wildcard hostname enabled](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_ecdn_config_wildcard_hostname_4.png) 5. Select a certificate type: **Self-Managed Certificate** or **eCDN-Managed Certificate**. ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_tip.png) Tip Use an **eCDN-managed certificate** to reduce renewal and expiration management overhead. If you select an eCDN-managed certificate and enable **Enable Wildcard Hostname**, all hostnames are auto-selected and disabled (greyed out). Wildcard hostnames require the validation method to be **TXT**. 6. Complete TXT validation to activate the certificate. For the eCDN-managed certificate, **TXT validation** is required to activate the certificate. We strongly recommend managing TXT validation by adding the DCV delegation CNAME record and its corresponding value to your authoritative DNS. These appear in the certificate summary pane. ![Certificates table showing wildcard hostname in Pending Validation with DNS records required for verification](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/b2c_ecdn_config_wildcard_hostname_5.png) When using DCV delegation, eCDN handles both initial certificate activation and subsequent renewals automatically. If you don't use DCV delegation, activate the certificate by adding both the certificate and wildcard TXT records to your authoritative DNS. ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_tip.png) Tip If you don't add the DCV delegation CNAME, you are responsible for manually renewing the TXT validation records in your authoritative DNS after every certificate renewal. It takes a few minutes for DNS propagation to complete and activate the certificate. The certificate's status changes to **Active** on the Certificate tab when the process is complete, and eCDN removes the activation records from display. After you complete all steps, every hostname associated with the domain serves traffic. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_important.png) Important A specific-hostname certificate takes precedence over a wildcard certificate. Create a specific-hostname certificate (for example, `shop.merchant.com`) even if a wildcard certificate (`*.merchant.com`) already exists. When both are present, the specific-hostname certificate takes precedence per established hostname priority rules. #### See Also - [Add Hostnames to an eCDN Zone](https://help.salesforce.com/s/articleView?id=cc.b2c_adding_hostnames.htm&release=264.0.0&type=5 "You can configure subdomains of the same zone on the same Salesforce B2C Commerce instance, or on different instances of different realms of the same retailer.")