大网数据广告活动
服务器运维问答

DKIM cname record name (generated by AWS SES) is > 63 characters which exceeds the DNS limit

· 52CE 我爱测

i am working on a client site that has a long domain name (25 characters). when setting up AWS SES i am unable to update the CNAME DKIM records on the DNS provider as the maximum length allowed for the name field is 63 characters…

问题原文

原帖链接 · vampiire · CC BY-SA 4.0

i am working on a client site that has a long domain name (25 characters). when setting up AWS SES i am unable to update the CNAME DKIM records on the DNS provider as the maximum length allowed for the name field is 63 characters (per the DNS spec).

AWS SES generates CNAME records that have name fields with 69 characters (XXX._domainkey.DOMAIN-NAME.COM). compounded with this is the client wants a subdomain email account setup which would bring the length to 75 characters.

has anyone encountered this before? is there a workaround? to be clear i am not talking about the CNAME value (which i understand can be split up with quotes). i am speaking about the CNAME name field itself.

已采纳解答

原帖链接 · erehwon studios · CC BY-SA 4.0

i also ran into this same issue yesterday, trying to insert AWS SES DKIM strings into enom host records, specifically the CNAME name field, and running into enom's self-imposed 60 character limit.

the solution that worked for me was to truncate the name field by removing the domain name at the end of the string. specifically, if your domain is "foo.com", AWS issues a name field like:

"[key]._domainkey.foo.com"

i replaced mine with:

"[key]._domainkey"

and my domain verified successfully. the DKIM parser doesn't seem to require (or infers) the domain name, i'm only guessing at the logic, but it worked for me. hope it works for someone else too.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2019-08-21)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。