Issues with DKIM records not being recognized for ActiveCampaign domain verification on Cloudflare

Hello Cloudflare Community,

I’m currently facing a challenge with verifying my domain for ActiveCampaign through DNS record updates on Cloudflare. Despite setting up the required records as instructed by ActiveCampaign, the DKIM records do not seem to be recognized. I’ve detailed the records below for clarity:

  1. DKIM1 Record
  1. DKIM2 Record


I have already set these records to DNS only (bypassing the proxy) to ensure they are directly accessible, but ActiveCampaign still does not recognize the DKIM records.

I’m reaching out for advice or suggestions on how to resolve this issue. Is there a step I might be missing, or is there a known delay or propagation issue with DNS records for DKIM verification on Cloudflare? Any guidance on how to ensure these records are correctly recognized by ActiveCampaign would be greatly appreciated.

Thank you in advance for your help and insights.

What is your domain?

oh my bad,

monmentordigital.com

Seems your issue is the same as someone else the other day. _domainkey.monmentordigital.com is delegated to infomaniak.com nameservers (maybe a previous setup imported when you set up Cloudflare).

Delete any NS records that appear in your Cloudflare DNS.

dig +trace +nodnssec -4 acdkim1._domainkey.monmentordigital.com

; <<>> DiG 9.18.20 <<>> +trace +nodnssec -4 acdkim1._domainkey.monmentordigital.com
;; global options: +cmd
.			72493	IN	NS	k.root-servers.net.
.			72493	IN	NS	j.root-servers.net.
.			72493	IN	NS	f.root-servers.net.
.			72493	IN	NS	e.root-servers.net.
.			72493	IN	NS	h.root-servers.net.
.			72493	IN	NS	b.root-servers.net.
.			72493	IN	NS	g.root-servers.net.
.			72493	IN	NS	i.root-servers.net.
.			72493	IN	NS	a.root-servers.net.
.			72493	IN	NS	c.root-servers.net.
.			72493	IN	NS	d.root-servers.net.
.			72493	IN	NS	l.root-servers.net.
.			72493	IN	NS	m.root-servers.net.

com.			172800	IN	NS	a.gtld-servers.net.
com.			172800	IN	NS	b.gtld-servers.net.
com.			172800	IN	NS	c.gtld-servers.net.
com.			172800	IN	NS	d.gtld-servers.net.
com.			172800	IN	NS	e.gtld-servers.net.
com.			172800	IN	NS	f.gtld-servers.net.
com.			172800	IN	NS	g.gtld-servers.net.
com.			172800	IN	NS	h.gtld-servers.net.
com.			172800	IN	NS	i.gtld-servers.net.
com.			172800	IN	NS	j.gtld-servers.net.
com.			172800	IN	NS	k.gtld-servers.net.
com.			172800	IN	NS	l.gtld-servers.net.
com.			172800	IN	NS	m.gtld-servers.net.
;; Received 864 bytes from 199.7.83.42#53(l.root-servers.net) in 7 ms

monmentordigital.com.	172800	IN	NS	noor.ns.cloudflare.com.
monmentordigital.com.	172800	IN	NS	casey.ns.cloudflare.com.
;; Received 385 bytes from 192.52.178.30#53(k.gtld-servers.net) in 12 ms

_domainkey.monmentordigital.com. 300 IN	NS	ns41.infomaniak.com.
_domainkey.monmentordigital.com. 300 IN	NS	ns42.infomaniak.com.
_domainkey.monmentordigital.com. 300 IN	NS	nsany1.infomaniak.com.
_domainkey.monmentordigital.com. 300 IN	NS	nsany2.infomaniak.com.
;; Received 159 bytes from 162.159.38.74#53(noor.ns.cloudflare.com) in 43 ms

;; Received 96 bytes from 83.166.143.75#53(ns42.infomaniak.com) in 22 ms
3 Likes

Just wanted to drop a huge thank you for sorting out the DKIM record issue for me. Seriously, your advice was spot on and solved everything!

It’s folks like you that make this community awesome – always ready to lend a hand and share what you know. I’m really grateful for your help.

Cheers for being amazing! Couldn’t have fixed it without you.

3 Likes