Failed to set DKIM TXT as DNS record

Question

I have a domain name whose DNS is edited through Google Cloud DNS. And I have a Google Apps account to work with this domain name.

I wanted to set up DKIM authentication, but when I try to save the corresponding TXT record, I get an error that is not valid.

I did the same before this and it worked perfectly. I checked the old setup and I saw that the old DKIM record is about half the length. The new one seems to be too long for a TXT record in the Google Cloud platform.

Anyone have a solution?

Answer 1

Yes, you must split the entry as described in this article:

https://support.google.com/a/answer/173535

If your domain provider limits the size of the TXT record value to 255 characters, you cannot enter the DKIM key as a separate record in DNS records. In this case, divide the key into several quoted text strings and enter them together in the TXT record value field. For example, split the DKIM key into two parts as follows:

  "V = DKIM1; k = rsa; p = MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAraC3pqvqTkAfXhUn7Kn3JUNMwDkZ65ftwXH58anno / bElnTDAd / idk8kWpslrQIMsvVKAe + mvmBEnpXzJL + 0LgTNVTQctUujyilWvcONRd / z37I34y6WUIbFn4ytkzkdoVmeTt32f5LxegfYP4P / w7QGN1mOcnE2Qd5SKIZv3Ia1p9d6uCaVGI8brE / 7zM5c /"
 "ZMthVPE2WZKA28 + QomQDH7ludLGhXGxpc7kZZCoB5lQiP0o07Ful33fcED73BS9Bt1SNhnrs5v7oq1pIab0LEtHsFHAZmGJDjybPA7OWWaV3L814r / JfU2NK1eNu9xYJwA8YW7WosL45CSkyp4QeQIDAQAB" 

Answer 2

I just ran into the same problem.

The google DKIM key text strings are longer than most other DKIM keys (possibly a higher bit) and will not fit into the 255 length limit for each TXT field.

A way around this is to make two TXT records and complete the first with \ or use ( in the first and ) in the second.

Google Cloud Computing DNS Analyzer does not seem to allow trial version \ ) or precedes ( .

There may be some way to avoid this in the Google Cloud DNS tool, but this is not obvious.

Good. I have a solution.

Be sure to only record TXT records and do not add multiple TXT records - this is a key step.

If you click "Add Item" when setting up a TXT record, it actually creates a different TXT record, and both records can resolve in any order, and DKIM will not check.

The trick is to put the broken lines in the first text input and break them into small enough parts that they all get in the correct sequential order.

Answer 3

Select the bit length "1024" when creating DKIM entries in the Gsuite admin console. It worked for me.