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

Website, Application, Performance
1

Hi, I have an urgent and serious issue. Cloudflare does not appear to be accepting the required domain key settings from Mailchimp. So I cannot get our domain authticated and this has been failing now for 4 days. I urgently need to know how to fix this. The domain key name needs to be this: k2._domainkey.mydomain.co.uk but whenever I click save it truncates it to just “k2._domainkey”. This is preventing authentication taking place and causing serious issues. Can anyone advise how this can be fixed? There are no clashes of names as these are unique settings in the DNS zone.

4

You should not enter the full name, only k2._domainkey, as your domain is automatically appended.

If you create a record for a subdomain, you would also only enter www as the name.

1 Like
5

Thank you for your response but mailchimp are insisting that the domain key name is incorrect as “k2._domainkey” and that it should be the full “k2._domainkey.coresciences.co.uk”. I suspect they are wrong but you can’t tell an ignorant person what they refuse to accept! Trouble for me is that I have no cloudflare support (except forum) and mailchimp don’t give seem to give a damn just saying it’s a cloudflare issue

6

That DNS entry does not exist when queried. The issue isn’t truncation though. Are you sure you are making these changes in the right account? In your DNS control panel on Cloudflare what are the listed nameservers?

7

They are the default cloudflare nameservers we were allocated on account setup. They are standard format cloudflare format (Not allowed to paste links here in that format.
How is this relevant. I’m sorry I’m not that technical myself, What do you mean in the right account? I am making these entires for the domain that requires them alogside the others it has previously required and which all work.

8

It’s working now.

k2._domainkey.coresciences.co.uk. 60 IN TXT     "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSu" "B0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;"
;; Received 486 bytes from 173.245.58.243#53(zita.ns.cloudflare.com) in 68 ms
1 Like
9

Sorry. I’m confused. What is working now? It’s still showing as only “k2._domainkey” in my settings. Where are you getting this infor from please?

10

Are you saying it’s working as it should, in which case it would have been all along and therefore mailchimp have got it wrong by simply saying it doesn’t look like the right name format in the settings?

11

Sorry you’re right I was testing on mobile and didn’t add TXT as the record type. :coffee:

2 Likes
12

Yes, otherwise I wouldn’t know the content of the dkim record.

You didn’t share your domain earlier, so I am unable to tell whether it was working before or not.

13

Ok thank you so should I copy and paste your result to mailchimp support to prove it is working and the issue muct be their end?

14

I recommend you test your email with https://mail-tester.com and share the result here.

Then I’ll be able to tell you whether you have any problems with your email setup.

15

Thanks but I’m not sire I understand what you mean. My emails are completely fine. I’m not having an issue with any emails. It is simply mailchimp not able to authenticate the domain at their end and they are saying it is to do with the CNAMEs that were entered for their authentication process

16

If the problem is with a CNAME record, why are we discussing your DKIM TXT record here?

1 Like
17

I have no idea, I never mentioned DKIM or TXT records

18

The issue is described at the top of the chat. Originally it was mailchimp declaring that cloiudflare was not saving the domainkey name in the right format. Soi they are blaming cloudflare. Your tests seem to contracdict this and that the format of the name is correct and the CNAME records are resolving correctly. If I understand correctly myself. In which case it now suggests a Mailchimp issue of failure to authenticate? Is that would you think?

19

You have created a TXT record for k2._domainkey. What cname were you supposed to create?

20

No they never asked me to create any text records they simply told me to add two CNAME records only, which I have done. except that where mailchimp say the Name should be k2._domainkey.coresciences.co.uk Cloudflare will not save it and trucates it to k2._domainkey only

21

Can you show a screenshot of your dns records, including the assigned cloudflare nameservers below?

Because you definitely have a dkim txt record for that name, not a cname.

23

How can I upload a screenshot here?