Additional custom domains

Every project has one primary custom domain (see Project settings → Custom domain). If you need the same quizzes and paywalls to be reachable from several subdomains — for example one per brand, per market, or per ad account — you can connect additional domains to the same project.

Plan requirements

• A custom domain is available from the Pro plan.
• Connecting more than one domain to a project requires the Advanced plan.

If your project isn't on Advanced, the cabinet shows this message instead of letting you continue:

Multiple domains feature is available in Advanced plan only.

To upgrade, contact your account manager or use the in-app chat.

If you don't see the Add additional domains button at all, the feature isn't enabled for your account yet — reach out to the web2wave team.

Before you start

• Your primary custom domain is already connected and working.
• Use a subdomain for every domain you add — for example quiz.yourdomain.com or start.yourbrand.com. Second-level (apex) domains such as yourdomain.com are rejected, exactly as they are for the primary domain.
• You have access to the DNS settings of each domain you want to connect.

Add an additional domain

1. Go to Projects and open the project.
2. Open the General tab and scroll to the Custom Domain section.
3. Click Add additional domains. The Add Additional Domain modal opens.
4. Enter the full subdomain you want to connect (for example quiz.yourdomain.com) and confirm.
5. Create the DNS record for that subdomain (see below), then wait for it to propagate.

Repeat for every extra domain — there is no limit in the interface on how many you add. Each domain needs its own DNS record.

As soon as you have at least one extra domain, an Additional Domains card appears in the General tab with the list of those domains.

DNS setup

Additional domains use the same DNS record as the primary domain. In your DNS provider (Cloudflare, Namecheap, GoDaddy, etc.) create:

If your DNS is hosted on Cloudflare, disable the proxy for this record (grey cloud, "DNS only"). A proxied (orange cloud) record prevents the SSL certificate from being issued, and the domain will keep failing verification.

DNS changes can take up to a few hours to propagate globally. You can monitor them at dnschecker.org.

Note: Don't forget to add every new domain to the verified domains list in your payment system (e.g. Stripe, Solidgate). Checkout will fail on a domain the payment provider doesn't know about.

Manage additional domains

In the Additional Domains card, each domain has:

• Check DNS — re-runs the CNAME check. Use it after you create or fix the DNS record instead of waiting for the status to refresh on its own.
• Show Details — shows the expected record values and the current status of the domain. Start here when Check DNS fails.
• Delete — disconnects the domain from the project. Any links that use it stop working, so replace those links first and remove the domain from your payment system's verified domains.

Troubleshooting

• The domain is rejected when you add it. Make sure you entered a subdomain (quiz.yourdomain.com), not the apex domain (yourdomain.com).
• Check DNS keeps failing. Confirm that the Host field contains only the subdomain label and not the full domain, that no other record (an A record or a second CNAME) exists for that label, and that the Cloudflare proxy is off. Then wait for propagation and run Check DNS again.
• The page returns ERR_SSL_VERSION_OR_CIPHER_MISMATCH, or the check reports "custom hostname does not CNAME to this zone." Reach out to the web2wave team for assistance, as with the primary domain.
• Checkout fails only on the new domain. The domain is most likely missing from the verified domains list in your payment system.

Related

• Project settings — primary custom domain and the rest of the project-wide settings.
• API key and webhooks — requests to the API go through your custom domain.