Introduction
Setting up a custom domain for your form can enhance your branding, provide a professional appearance, and improve user experience.
This document will guide you through the process of configuring a custom domain in your form settings tab. Additionally, it will provide information about the types of domains accepted, specifically root domains and subdomains, and explain how to configure your DNS provider with the necessary records.
Configuring a Custom Domain
I. Types of Domains Accepted
When configuring a custom domain for your form, the following types of domains are accepted:
- Root Domain: A root domain is the main domain for your website or application, such as "example.com". It does not contain any subdomains and represents the highest level in the domain hierarchy.
- Subdomain: A subdomain is a prefix to the root domain and allows you to create separate sections or subdivisions of your website or application. For example, "blog.example.com" is a subdomain of "example.com".
Please note that slugs, which are additional path components in the URL (e.g., "example.com/blog"), are not accepted for custom domain setup at the moment. You can request for this feature here.
You also do not need to include the protocol (e.g. “https://” or “http://”) when adding the custom domain.
II. Configuring DNS Provider with Records
After adding a custom domain, you should see a To configure your DNS provider correctly, follow these general steps:
- Log in to your DNS provider's website or administration panel.
- Locate the DNS management section or a similar area where you can edit DNS records.
- Add a new DNS record, usually a type called "CNAME" (Canonical Name), to map your custom domain to your app's URL or endpoint.
- Enter the necessary details for the CNAME record:
- Host/Name/Label: This should be the desired subdomain or leave it blank for the root domain.
- Target/Points to/Value: Enter the URL or endpoint provided by your app's settings for custom domains.
- Save the changes or publish the DNS record.
- Wait for the DNS changes to propagate, which can take some time (usually a few minutes to several hours). During this time, your custom domain may not be accessible.