Would someone please be able to shed some light on why this is necessary with Route53 when other DNS services can handle the long strings properly?
I am still pretty new to AWS, but man it feels like so many things just don't work as they should.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
The suggested solution does not work. Route 53 adds a space to the string at the point of the split.
Original TXT record: ...lNJ3n2C2kw/IPwt... Results from dig: ...lNJ3n2C" "2kw/IPwt...
As this is a DKIM record, the space causes the validation to FAIL.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
This does work - but the instructions here are not exactly correct. This statement:
Split the DKIM key value into two parts, and then enclose each part in double quotation marks.
Should say this:
Split the DKIM key value into two parts, and then enclose each part in double quotation marks. Be sure to add a single blank space between the two strings.
So do not do this: "first string""second string" -- make sure you do this: "first string" "second string"
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
This is really poor. If it's common enough to have a knowledge base workaround then fix the root issue.
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Ive tried few different ways of splitting it and i keep getting the test back with a space between where i split
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Relevant content
- Accepted Answerasked a month ago
- asked a year ago
- asked 5 years ago
- Accepted Answerasked 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago