Email not Authenticated on Cloudflare end-Cloudflare needs to update/propogate

Hi, I have been trying to authenticate my gsuite gmail for 2 weeks now, and have been unable to. I’ve spoken with Gsuite support twice now and they said to ask Cloudflare support to fix it (update the records) on their end. On Gsuites send, everything is 100% all set.
Problem is, I cannot get ahold of any support at cloudflare. I have tried to email to no avail. I tried to upgrade to 25/month, and it wants me to upgrade to business, at 250.00 per month. I cannot afford that.
Does anyone have any idea how to speak with a person at cloudflare without having to pay a fortune OR how to get the records to update? Please help, anyone!

Domain?

Have you ensured all of your mail related records for gmail are set to DNS Only :grey: ?

If everything on Gsuite’s end is 100% all set, what isn’t working? What records do they believe you need to update?

1 Like

I have updated the DKIM value from Gsuites Admin Console, to Cloudflare DNS records correctly and the DKIM value from admin console is matching exactly with the value which I have updated in cloudflare. The DKIM record has been updated correctly but it still is not authenticating. Please correct it from Cloudflares end because it is not authenticating from Cloudflare’s end. Could you all screen share with me to make sure it works?

What is the domain?

fasttrackpro.com
is it possible to do a screen share? or a phone call?

Are you still there?
I have already provided the domain name, fasttrackpro.com, are you able to fix it on your end? PLEASE!
I have Gsuite on the phone with me, so if you are able to fix it on your end that would be great and is the only way as we are stuck here.

It is not. I don’t work for Cloudflare or provide personal consulting services. I just volunteer in the forums on occasion.

https://cf.sjr.org.uk/tools/check?dd6c796536ed4cdb89f71313877e429b#dns

Are you sure you’ve copied the correct values to the correct records exactly as they exist in the Google search console? You can see what is being returned by Cloudflare DNS and compare that to what Google expects. If you’re copying it correctly, then you need to make sure you’re in the correct account (that the nameservers match what is returned in DNS) because either you aren’t adding the correct entries or you are in the wrong account.

1 Like

Cloudflare does not make changes on behalf of customers. Your records don’t appear to be ones that would be expected for several of the record types. Please review them carefully… perhaps delete them and recreate them by using copy & paste from the Google console.

1 Like

The DKIM value is configured properly from Admin Console to Cloudflare and I have cross checked that the value is correct and matching, and also I have deleted the existing DKIM record value and recreated that value in cloudflare.
So, everything is configured properly from my end but still the DKIM is not authenticating from cloud flares end and it is not being reflected as well.
How can I have DKIM authenticated by cloudflare. Is there a direct contact support that you know of that I can reach out to cloudflare?

_domainkey.fasttrackpro.com is delegated to other nameservers. Delete any NS records for _domainkey in your Cloudflare DNS.

dig +short _domainkey.fasttrackpro.com ns
ns1.namefind.com.
ns2.namefind.com.
1 Like

Gsuite support says the only records that matter for sending and receiving of emails are MX, SPF, DMARC and DKIM
My SPF, MX records are already configured properly.
Currently the issue is (as I mentioned earlier) related to the DKIM records that are not getting authenticated from Cloudflare’s end
We’ve already configured the proper values for DKIM

…and they are being ignored because…

…so you need to…

1 Like

ok I just did that

Then it appears…
https://cf.sjr.org.uk/tools/check?bb40f36f051c49b4afd66754ccc95255#dns-mail

1 Like

Thank you both so much
I believe it is working now on Gsuites end. We did delete some NS records. I really appreciate your help!!!

2 Likes

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