Skip to main content

Can't paste full DKIM key in Zone Editor - Character limit issue?

Comments

4 comments

  • cPRex Jurassic Moderator
    Hey there! If you click "Edit" below the record you'll see an option to break it up into two parts like this screenshot (this is a fake domain, so it's fine that I'm putting these out there): That's normal for a cPanel system, and if you check the record on the command line you'll see this: default._domainkey 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA04a4a/YymB1ROdKjskOnSBT7MqZdzabMb4nniATKG/Epuu9P+fjgIpuQ6bOlPNjxD0eUkCac0LSPv9kud6jIvBd3EXTPjzePndoy123XNcWQZ0aDvUyjw9G4h7bcu/A6+9uKISMmmW9gETxbubcUd6++davo//vc+AiMcUlidzken5f2OT9or/hG1bcpxkyc8" kg6zthzXXEXJMkMVIdsf3XNwgd3QM6SLJiEmxZFJatDJopjCI7VY7msksbXwrF/bMZPnw5NtnMcmaYP4g1jS/QbBwJKUL3IJk8ggo1DG5dRlmCGVCYU13ZBUWzyM1vFKs7EdNFVngCW9R18ZOEV9QIDAQAB\;
    Is there a reason you're trying to paste a record into cPanel instead of letting the software create one for you?
    0
  • bz87
    Thanks this works!
    0
  • Reado
    This isn't a solution; surely breaking up the string leaves room for error? The last system you had didn't require strings to be broken up. It makes no sense why there's a character limit.
    0
  • cPJustinD
    Hello Reado!
    The last system you had didn't require strings to be broken up.

    I wanted to offer some clarification here. In v94, the DNS Zone Manager would automatically split TXT records that were entered in the interface behind the scenes after the record was saved. In v96, we introduced multi-part TXT records. While this is great, it seems that this is now the enforced default, and there is no way to add a TXT record in a single, full line if it exceeds 256 characters. We've published an internal case with our development team on this, CPANEL-37236. We've also published an article with additional information on this case here: Why are DKIM TXT records split?
    0

Please sign in to leave a comment.