I have created a CNAME for the root domain, this is required for our salesforce website utilising CNAME Flattening, when doing a dnslookup the CNAME is not resolving and causing issues with the salesforce portal.
What feature, service or problem is this related to?
Note that it’s not possible for them to see the CNAME at the root directly, only IP addresses, as a CNAME at the root is always flattened to return IP addresses. (Although as I say at the moment, nothing is returned).
Here is the DNS record…
I’m not very good with DNS records so please excuse my ignorance.
the www cname is inplace so clients can direct to www.clementsandchurch.co.uk… this is working as we expect.
we are trying to ensure clients that type HTTPS://clementsandchurch.co.uk are also able to get to the site… Salesforce have told us that a CNAME on the root would acheive this, we then have to go through some configureation of the salesforce portal, but without the record being resolved the salesforece side just errors.
Could you please try changing the name of the record from clementsandchurch.co.uk to @?
(On saving the @ will automatically be replaced by your domain again)
Also, could you do the content of the CNAME again? But this time, please type it instead of doing copy/paste.
That does not resolve. Only the www version resolves.
[add] Likely there is some automated process where Saleforce checks for the CNAME record before creating the target. This won’t work for the apex domain since it can only ever return A/AAAA records and not CNAMEs. I seem to recall someone else having similar a little time ago.
Check with Salesforce how they handle these records at the apex.
You’ll have to ask them then, as clementsandchurch.co.uk.00d1t000000ehikeas.live.siteforce.com does not resolve so Cloudflare can’t return the flattened result.
[add] Try adding www to the front of it. Since they can’t see the CNAME anyway, that at least resolves.
As clementsandchurch.co.uk redirects to www.clementsandchurch.co.uk anyway it’s probably not an issue. You could do the same redirect on Cloudflare instead as here…
Then Salesforce will just see the requests on www.