How do I resolve the "CharacterStringTooLong (Value is too long) encountered with {Value}" error that I receive when creating a TXT record using DKIM syntax?
"I tried to create a DKIM text resource record that a third party provided in my Amazon Route 53 hosted zone. However, I got the following error: "CharacterStringTooLong (Value is too long) encountered with {Value}.""
"I tried to create a DKIM text resource record that a third party provided in my Amazon Route 53 hosted zone. However, I got the following error: "CharacterStringTooLong (Value is too long) encountered with {Value}."Short descriptionDNS TXT records can contain up to 255 characters in a single string. You must split TXT record strings that are over 255 characters into multiple text strings within the same record.Note: If the value is split, then DKIM functionality doesn't break.Resolution1.    Open the resource record that you received from your third-party provider.2.    To adhere to the 255 character maximum for a single Route 53 TXT record, split the DKIM key value into two parts. To do this, follow these steps:Copy the DKIM key value from the resource record.Paste the DKIM key value in a new line of a text editor.Split the DKIM key value into two parts, and then enclose each part in double quotation marks. For example, the value for "long_string" is split into "long_""string".Note: Don't add a line break between the two parts.3.    Open the Route 53 console.4.    In the navigation pane, choose Hosted zones.5.    Select your hosted zone.6.    Choose Create Record Set.7.    In the Create Record Set panel, complete the following steps:For Name, enter the domain key identifier.For Type, choose TXT.For Alias, keep the default selection of No.For TTL, enter the number of seconds. The default value of 300 is typically sufficient.For Value, copy the split DKIM key value that you created in step 2 from your text editor. Paste the split value in the Value field.Choose Create.8.    Use dig or nslookup to confirm that the TXT record is presented as a single entry.dig:$ dig selector_key_1._domainkey.domain.com txt ...;; ANSWER SECTION: selector_key_1._domainkey.domain.com. 60 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz1xhXc+vJKhQJUch86o8Ia2+L/AYo4d5eRVrPMMWzz4EiM4eB4QC1hJ83YMCHLv5dDN2lJ3KWSd5tGOxF/FRj1KdN+Jdf+BVwuklBFO8IrDtMz/lk2CJjF8jlgIUmQAjs3lc/8Bee+" "IQeB2tLX9UWvQMpI3aZuh6Ym6hcvLnbEkALWaMQvqwgxZs1qF6t5VKMjWeNNWIScyNTYL4Ud8wDiBcWh492HustfGUxrl5zmRfEl8BzCbrOqpKPLBmk/xrHRw9PHIJyYOaZA2PFqVcp6mzxjyUmn0DH9HXdhIznflBoIOLL1dm77PyDOKdEWRkSLMCA72mZbFr9gxda72ocQIDAQAB"nslookup:    > nslookup -q=TXT selector_key_1._domainkey.domain.com...Non-authoritative answer:selector_key_1._domainkey.domain.com.    text =        "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz1xhXc+vJKhQJUch86o8Ia2+L/AYo4d5eRVrPMMWzz4EiM4eB4QC1hJ83YMCHLv5dDN2lJ3KWSd5tGOxF/FRj1KdN+Jdf+BVwuklBFO8IrDtMz/lk2CJjF8jlgIUmQAjs3lc/8Bee+"        "IQeB2tLX9UWvQMpI3aZuh6Ym6hcvLnbEkALWaMQvqwgxZs1qF6t5VKMjWeNNWIScyNTYL4Ud8wDiBcWh492HustfGUxrl5zmRfEl8BzCbrOqpKPLBmk/xrHRw9PHIJyYOaZA2PFqVcp6mzxjyUmn0DH9HXdhIznflBoIOLL1dm77PyDOKdEWRkSLMCA72mZbFr9gxda72ocQIDAQAB"Related informationTXT record typeFollow"