Domainkey name being truncated (not saved) by cloudlflare - HELP PLEASE!


Figured it out

They are defnitely CNAMEs

That screenshot does not include your assigned nameservers.

Are they vin and zita or others?

Yes they are vin and zita

Just had this in from mailchimp

They have also said this. Not sure if it is correct when no other providers needing to authenticate (Microsoft, google and sengrid etc) have ever had such issues or needed anything to be ā€œpublicā€ that isn’t already set.

The provider to your domain has to make the domain itself public in order to be able to use it on external sites like ours, your domain providers soundlcoud needs to specifically make your domain public. Its not that the CNAME is incorrect or the fields are wrong its that we can not get access to your domain so we can not authenticate it.

You can send them the direct link like I just did here with you and let them know you need your domain to be public.
Being able to access the site or use the domain from other places is not the same as the coding structure that allows the authentication to take place.

They just use the term public for allowing access to your domain.

Your k3 record is misspelled, there is a dot missing.

If you look at dns settings in cloudflare, what option do you have selected for cname flattening? It should be apex only.

1 Like

Thanks for that spot. That was me a little earlier today when checking editing the domain name. The dot is back in. I’ve checked CNAME flattening and it was at the default setting of flatten all. Why is that a bad thing if a default setting? I have set it to apex only now as you suggest.

Also, what do you think about all this publc domain setting talk they are now blaming this all on? What do you make of that?

Flatten all is not the default setting. It is not even available on free plans.

They couldn’t find the cname records because of the flattening option. I have no idea what they mean by the domain not being public.

2 Likes

Wow!! How bizarre. having changed away from flatten all and selected Apex only, that other option to flatten all is not there anymore. I wonder if it was set from before when we once had a paid plan and got stuck that way when we came off it? Anyway with that swicthed off it has suddenly authenticated!!! So they clearly don’t know what they are talking about at mailchimp and grasping for any explanation they can and getting it wrong every time. But you have resolved the issue!!! I’m so grateful to you, Thank you very much for your help and sticking with me. I really appreciate it :slight_smile:

2 Likes

Why would anyone even on a paid plan want a Flatten All option when it has that kind of negative impact??

It makes DNS lookups faster, and verifying a domain should really be done via txt records.

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.