If you have a main domain that is not meant to be connected to Webflow, but you want to connect a subdomain to Webflow, you'll need to make the necessary DNS (Domain Name System) changes. Here are the required records to connect a subdomain to Webflow:
1. CNAME record:
To point the subdomain to the Webflow servers, you'll need to create a CNAME record. This record acts as an alias and redirects the subdomain traffic to Webflow's servers. In your DNS settings, create a CNAME record where the "Name" field is your desired subdomain (e.g., "subdomain") and the "Value" field is "proxy-ssl.webflow.com".
2. A records (optional):
Depending on your needs, you might also want to create one or more A records to ensure proper handling of subdomain traffic. These records can be used to map the subdomain to a specific IP address.
For example, if you want to use a naked subdomain (e.g., https://subdomain.example.com) without the "www" prefix, you can create an A record that points to the Webflow IP address. This can be helpful if you want to redirect visitors to the subdomain directly, rather than having them go through the "www" subdomain.
To create an A record, enter the desired subdomain (e.g., "subdomain") in the "Name" field and the appropriate Webflow IP address in the "Value" field. You can obtain the Webflow IP addresses from your Webflow project settings under the "Custom domains" section.
3. SSL certificate:
Webflow automatically provides SSL certificates for all sites hosted on their platform. Once you've set up the CNAME and A records, Webflow will generate and manage the SSL certificate for your subdomain. This ensures a secure connection and enables HTTPS for your subdomain.
Remember that DNS changes might take some time to propagate worldwide, so it's normal if you don't see the changes immediately. It's always a good idea to double-check your DNS settings and reach out to Webflow support if you encounter any issues.