Email issue and DKIM

Hello,
I’m currently using the “acumbamail” service to manage the sending of email campaigns and I’ve just realized that the opening rate is very poor, apparently many emails aren’t getting through. In my search, I found that the “DKIM” was not configured.
So I added it by going to “record”, “add record”, Type: “CNAME”, Name: “(name given by acumbamail)”, Address: “(address given by acumbamail (dkim.acumbamail.com))”.
Once registered, I waited 48 hours, checked in acumbamail and the registration was apparently not taken into account.
I did the same thing, choosing “TXT” for the Type.
What should I do? Do I need to contact my web host (Infomaniak)?
Thank you very much for your help.

Welcome to the Cloudflare Community. :logodrop:

Make sure the DKIM CNAMEs are set to :grey: DNS Only.

2 Likes

Thank you very much! I just made the change, fingers crossed it works ! :slightly_smiling_face:

1 Like

Hello,
After waiting for the indicated delay for the change to be taken into account the DKIM has apparently still not been detected and is not taken into account by my emaling tool :confused:
The CNAMEs pointing to my host are still on “Proxied”, I’ve only changed those corresponding to my Dkim (otherwise there’s a security problem, apparently). Do you have any idea where the problem might be coming from ?

You don’t need to wait that long. You can query the authoritative servers almost immediately after you make any change.

If you would like Community members to report on the reqults of such queries, please share your domain name and the records you were asked to create so that we may test.

2 Likes

Okay, thank you very much! My domain name is “dessiner-la-nature.com” and the Dkim features are :
Host/Name: “acumbamail._domainkey.dessiner-la-nature.com”
Type : "CNAME
Value : “dkim.acumbamail.com
Here are screenshots of the requested settings

image

$ dig +noall +auth _domainkey.dessiner-la-nature.com. @arturo.ns.cloudflare.com
_domainkey.dessiner-la-nature.com. 300 IN NS    ns41.infomaniak.com.
_domainkey.dessiner-la-nature.com. 300 IN NS    ns42.infomaniak.com.

These two NS records are delegating all of “_domainkey.dessiner-la-nature.com” (including it’s sub-domains), and sending it towards Infomaniak’s two name servers.

That would mean to have any effect of changes on “_domainkey.dessiner-la-nature.com”, or any of it’s sub-domains, including, but not limited to e.g. “acumbamail._domainkey.dessiner-la-nature.com”, the change would need to be made on Infomaniak’s end, with the current set up.

However, it appears that Infomaniak’s name servers do not even respond to DNS queries for that delegation:

$ dig _domainkey.dessiner-la-nature.com @1.1.1.1
[...]
; EDE: 22 (No Reachable Authority): (at delegation _domainkey.dessiner-la-nature.com.)
; EDE: 23 (Network Error): ([2001:1600:0:aaaa::3]:53 rcode=REFUSED for _domainkey.dessiner-la-nature.com A)
$ dig _domainkey.dessiner-la-nature.com @8.8.8.8
[...]
; EDE: 23 (Network Error): ([83.166.143.74] rcode=REFUSED for _domainkey.dessiner-la-nature.com/a)
; EDE: 23 (Network Error): ([83.166.143.75] rcode=REFUSED for _domainkey.dessiner-la-nature.com/a)
; EDE: 23 (Network Error): ([2001:1600:0:aaaa::3] rcode=REFUSED for _domainkey.dessiner-la-nature.com/a)
; EDE: 22 (No Reachable Authority): (At delegation _domainkey.dessiner-la-nature.com for _domainkey.dessiner-la-nature.com/a)

As such, …

I would delete that two NS records from your Cloudflare configuration, that is pointing “_domainkey.dessiner-la-nature.com” towards “ns41.infomaniak.com” and “ns42.infomaniak.com”.

3 Likes

Thank you ! It was a bit complicated to set up Cloudflare with Infomaniak (my site was taken offline). Isn’t there a risk that my site will be offline again if I delete these 2 NS records ?

No.

  1. Your website have no relation to those records, unless you browse using something like “https://_domainkey.dessiner-la-nature.com”, or “https://alfa.bravo.charlie._domainkey.dessiner-la-nature.com”, or any other address that ends with “._domainkey.dessiner-la-nature.com”, which sounds very unlikely.

  2. As the DNS, as demonstrated above, does not work for “https://_domainkey.dessiner-la-nature.com”, things that would eventually break with the deletion of those NS records, would already be broken right now.

2 Likes

Thank you very much ! It works well, and sorry for the questions, technically I really do not master. I couldn’t have done it without your help @epic.network and @DarkDeviL, thank you !

2 Likes

Glad to hear that!

You don’t need to apologize for that. Asking, just like you did, is the thing you should do, in such situations!

You’re welcome!

1 Like

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