When setting up HubSpot hosting alongside an existing CNAME record for www, you can run into conflicts because a subdomain (like www) can only have one CNAME record at a time. Here's how you can resolve the issue:
1. Understand the Conflict
- A CNAME record maps a subdomain (like www) to another domain name.
- Only one CNAME record can exist for a subdomain at a time.
- If your domain provider already uses the www CNAME (for example, pointing to Webflow, Shopify, or somewhere else), you cannot add another CNAME for HubSpot without breaking the original setup.
2. Choose Who Will Manage www
- Decide if you want www to go to Webflow, HubSpot, or another platform.
- You can't serve www from both Webflow and HubSpot simultaneously without a reverse proxy, which is complicated and not usually recommended.
3. Set Up a New Subdomain if Needed
- If you want to keep www pointing to Webflow and still use HubSpot, create a different subdomain for HubSpot.
- Common choices: info.yourdomain.com, resources.yourdomain.com, or blog.yourdomain.com.
- Create a CNAME for the new subdomain pointing to HubSpot as per their instructions.
4. Update Your DNS Settings
- In your DNS manager (e.g., GoDaddy, Cloudflare, etc.), add a CNAME record for your new subdomain.
- Example: info.yourdomain.com → [HubSpot provided CNAME target].
- In HubSpot, connect the new subdomain under Settings > Domains & URLs.
- In Webflow, continue managing www.yourdomain.com under Hosting > Custom Domains.
6. (Optional) Redirect Traffic if Needed
- If you want your Webflow website to link to your HubSpot landing pages on info.yourdomain.com, set up links accordingly.
- If you need all www traffic to go to HubSpot instead, you must remove the existing CNAME in your DNS and replace it with HubSpot’s.
Summary
You cannot have two CNAME records for www. You must either (1) switch www fully to HubSpot, or (2) set up a new subdomain like info.yourdomain.com for HubSpot. Managing the subdomain wisely will let you use both Webflow and HubSpot without DNS conflicts.