What are the required records to connect a subdomain to Webflow if the main domain is not meant to be connected?
TL;DR
- Set a CNAME record for your subdomain (e.g., blog) pointing to proxy-ssl.webflow.com.
- Add the full subdomain (e.g., blog.example.com) in Webflow’s Hosting settings under Project Settings.
To connect only a subdomain (like blog.example.com) to Webflow—without connecting the main domain (example.com)—you need to set specific CNAME and optionally A records, depending on your setup.
1. Use a CNAME Record for the Subdomain
- For most subdomains, Webflow recommends using only a CNAME record.
- Set the host to your subdomain (e.g., blog if your subdomain is blog.example.com).
- Point it to:
proxy-ssl.webflow.com
2. Optional A Records (Only If Required by DNS Provider)
- Some DNS providers don’t allow CNAMEs for root domains, which is not relevant here, but if your DNS provider requires A records for subdomains, use the following:
- A record pointing to: 75.2.70.75
- A record pointing to: 99.83.190.102
- However, most DNS setups for subdomains only need the CNAME.
3. Add the Subdomain in Webflow Hosting Settings
- Go to Project Settings in your Webflow project.
- Under the Hosting tab, click + Add Custom Domain.
- Enter your full subdomain (e.g., blog.example.com).
- Do not add just the root domain (example.com) if you don’t plan to connect it.
4. Set the Default Domain (Optional)
- If you are using multiple domains in Webflow, you can optionally set the subdomain (e.g., blog.example.com) as the default domain.
Summary
To point only a subdomain to Webflow without affecting the main domain, use a CNAME record pointing your subdomain (e.g., blog) to proxy-ssl.webflow.com, and then add the full subdomain in your Webflow project settings under Hosting. A records are typically not needed unless your DNS provider requires them for subdomains.