Hey @aitortomas , Yea - I think the misunderstanding is that the CNAME update that is required is for the DCV not for the traffic routing and is not asking you to update where your proxy is pointing.
What does not need to change:
- Your www points to your proxy server or CDN (Fastly)
- Fastly routes traffic to multiple origins, one of those origins is a CNAME record like {hubID}.sites-proxy.hscoscdn40.net - this actually hosts the content
What does need to change:
- In the past, to prove domain ownership you could have followed an HTTP challenge or you could have updated your DNS with a TXT record that looked like Record: “cf-custom-hostname.mulligandevelopment.io” Value: “655f6c48-bd6a-4d2f-88a2-d5c4ef5070d7” as well as a CNAME like Record host: _ca3-0bf93ffdd5b24db6b793475620821cb3.tc; Value: dcv.digicert.com.
- Now, you need to create a NEW DNS CNAME record to control the DCV process that will look like this: Record host: _acme-challenge.rp Value: rp.robertpainslie.com.07e5b8acaef7b01e.dcv.cloudflare.com
- You very likely do not already have a CNAME record at the host of this new “acme_challenge” host and if you DO, then you can update the value to be this new CNAME host pointing at the cloudflare.com value.
- The values are provided to you
Once you’ve added the DNS record for the “acme_challenge” CNAME, then you run the verification in HubSpot.
Does that help clear things up? Feel free to DM me any screenshots of your setup if things aren’t clear. Also, if you provide your HubID I may be able to take a look at your Domains Manager and confirm what records you need.
Also - this should be a process that HubSpot Support can help you with identify the right records in order to prove DCV ownership for your domain - open up a chat/email or call with them. They won’t be able to help with your proxy itself, but if you highlight that you need to understand what DNS records are needed to prove domain ownership, they should be able to help with that.