DKIM records are not propagating

What is the name of the domain?

bylittle.com

What is the issue you’re encountering

DKIM records are not propagating and I can’t authenticate my email.

What steps have you taken to resolve the issue?

We recently changed domains (from bylittle.io to bylittle.com) and our emails have been flagged as spam or quarantined ever since.

I already contacted Google Workspace support, who guided me through adding SPF, DKIM, and DMARC records.
All of them work except for the DKIM record, so I can’t authenticate my email, and some of my clients’ inboxes are still flagging it as spam.

Help!!

What feature, service or problem is this related to?

DNS records

Screenshot of the error

_domainkey and _dmarc are delegated to other nameservers…
https://cf.sjr.dev/tools/check?2e7ed79dde394f0f8d300fa609717b75#dns-mail

Either set those records in the delegated nameservers, or remove the NS records for _domainkey and _dmarc from your Cloudflare DNS for the records set in your Cloudflare DNS to be used.

3 Likes

Wow, SJR, thank you so much!! How should I do what you’re suggesting without messing it up? Could you kindly lay out the steps for me, please?

NS records that are delgating mail-related records have been imported from your previous DNS when you set up Cloudlfare. In most cases it seems users don’t want that and instead want to set the mail DNS records in their Cloudflare DNS. In that case, delete any NS records in your Cloudflare DNS.

If there is a reason why you need the delegation (maybe you are still using that DNS provider as your mail provider and need them to manage the related DNS records for you), then you need to set the records in their DNS.

I can’t know which one you want to do, it’s up to your setup, but as you seem to be using Google for your mail, likely the first one is what you want to do.

1 Like

Perfect, SJR! I really appreciate your input. Thank you so much!

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