Skip to content

Knowledgebase

Publishing cPanel DKIM when DNS is hosted elsewhere

cpanel-whm, email

DKIM signs outgoing mail so recipients can verify that the signed message was authorised by the signing domain. When DNS is hosted elsewhere, cPanel can provide the public record but cannot necessarily publish it to the live zone.

Check access and requirements

Confirm that the relevant mail actually leaves through this server. Keep private signing keys secret and identify the authoritative DNS provider. A public DKIM TXT record is intended for DNS; the private key is not.

01 Publish cPanel DKIM when DNS is hosted elsewhere

  1. Open Email Deliverability > Manage for the domain and locate the DKIM section. Generate the local key if the interface requires that step.
  2. Copy the provided selector/name and full public TXT value. Retain the exact selector because receivers query that name.
  3. Create or update the record at the authoritative provider. Check whether its name field automatically adds the domain to avoid duplicating the suffix.
  4. If the provider splits a long TXT value into quoted segments, ensure the resulting logical value remains complete. Do not omit characters to make the field shorter.
  5. Wait for DNS caching, send a fresh message through this server and inspect the recipient’s authentication results and DKIM signing domain.

02 Example: avoid adding the domain name twice

Suppose cPanel supplies the illustrative record name selector1._domainkey.example.com. If the external DNS form automatically appends example.com, the relative name to enter is selector1._domainkey. After saving, the public record must appear at the full intended name.

It must not become selector1._domainkey.example.com.example.com. A provider that accepts complete names may use a different entry format, so inspect its resulting record name. Use the actual selector and full public value supplied by your cPanel account, not the sample selector in this example.

Confirm the expected result

The public DNS record should match the server’s signing key and the new message should show a valid signature. A message sent by a separate platform may use that platform’s own selector and setup.

Resolve setup problems

If verification fails, compare the exact selector, public value and authoritative answer. After a key rotation, old cached records can briefly disagree with new signatures. Coordinate rotations with the provider instead of regenerating repeatedly during diagnosis.

Does DKIM encrypt a message?

No. It authenticates a signature over selected message content. Transport encryption and end-to-end message encryption address different needs.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support