Category

How to Setup DKIM for BoldDesk

Updated:

DKIM (DomainKeys Identified Mail) is an email authentication standard that helps recipient mail servers verify that an email was sent by an authorized sender and has not been altered during transit. DKIM works by adding a digital signature to outgoing emails, which is validated using public DNS records published by the domain owner. Configuring DKIM for your custom support email domain in BoldDesk improves:

  • Email deliverability
  • Sender reputation
  • Protection against email spoofing
  • Successful delivery of ticket notifications and automated responses

Incorrect DKIM configuration can cause email authentication failures, which may impact the delivery of ticket notification emails even when BoldDesk successfully sends them.

Check out this video tutorial.

Prerequisites

Before configuring DKIM:

  • A custom support email domain must already be configured in BoldDesk.
  • You must have access to your domain’s DNS management portal.
  • The domain must not be a public email provider such as Gmail, Yahoo, or Outlook.com.

Configure DKIM in BoldDesk

To set up DKIM in BoldDesk, please follow the steps below:

  1. Open DKIM Settings

    • Navigate to Admin → Emails → DKIM Settings.
  2. Select the Domain

    • You will see all custom domains configured in your BoldDesk account.

    • Expand the domain for which you want to enable DKIM verification.

      DKIM Page Configuration.png

  3. Copy the Generated DKIM Records

    • BoldDesk generates multiple CNAME records required for DKIM authentication.

    • Copy all generated records exactly as displayed.

      Copy Domains.png

  4. Add the Records in Your DNS Provider

    • Log in to your DNS hosting provider and create the CNAME records provided by BoldDesk.
      Type Name Value
      CNAME az7wfrq52echrymduyqozjb3fazrte64._domainkey az7wfrq52echrymduyqozjb3fazrte64.dkim.example.com
      CNAME 6brep3mo34rxkjso6vpsvw2jcbdbrpbz._domainkey 6brep3mo34rxkjso6vpsvw2jcbdbrpbz.dkim.example.com
      CNAME qie4u2iig45wjizbrwqyl4na4b6lxiyd._domainkey qie4u2iig45wjizbrwqyl4na4b6lxiyd.dkim.example.com
      CNAME bolddeskdomainkey dkim.bolddesk.com

Some DNS providers automatically append your domain name to the host field. Review the DNS provider documentation before entering the DKIM record names.

  1. Verify DKIM Status
    After adding the DNS records:

    • Return to Admin → Emails → DKIM Settings.

    • Click Check Status.

    • Wait for DNS propagation if verification does not succeed immediately.

      DKIM_settings.png

  2. Things to keep in mind:

    • Domain records may take up to 72 hours to reflect.
    • You cannot generate DKIM keys for free email domains that you do not own, such as Gmail or Yahoo.
    • If you do not have any custom support emails configured in BoldDesk, no domain will be listed on this page.
    • DKIM is already configured for BoldDesk default support email addresses that end in bolddesk.com, so you can’t configure that.
    • CNAME records should not be used for root domains—only subdomains.
    • You can only have one CNAME record per subdomain.

Common DKIM Configuration Mistake

DNS Provider Automatically Appending the Domain

One of the most common causes of DKIM verification failures is entering the fully qualified domain name (FQDN) in the DNS record’s Name/Host field when the DNS provider automatically appends the domain name.

This can result in a duplicated DNS record such as:

az7wfrq52echrymduyqozjb3fazrte64._domainkey.example.com.sg.example.com.sg

Instead of the correct record:

az7wfrq52echrymduyqozjb3fazrte64._domainkey.example.com.sg

Correct vs. Incorrect Record Format

If Your DNS Provider Automatically Appends the Domain

Enter only the subdomain portion in the Name/Host field.

Correct

az7wfrq52echrymduyqozjb3fazrte64._domainkey

Incorrect

az7wfrq52echrymduyqozjb3fazrte64._domainkey.example.com
If Your DNS Provider Requires the Full Host Name

Enter the value exactly as provided by BoldDesk:

az7wfrq52echrymduyqozjb3fazrte64._domainkey.example.com

After saving the record, verify how it appears in your DNS management portal. If the domain name is duplicated (for example, example.com.example.com), the record was entered incorrectly and should be deleted and recreated using the appropriate format for your DNS provider.

Troubleshooting DKIM Verification and Email Delivery Issues

Issue Verification Steps
DKIM verification remains pending or fails Ensure the records are created as CNAME records and that the Name/Host and Value/Target exactly match the values generated in BoldDesk. Verify there are no typos, extra spaces, missing characters, duplicated hostnames (for example, domain.com.domain.com), or conflicting DKIM-related records using the same host value.
DNS records appear correct but verification still fails Confirm the DKIM CNAME records are publicly resolvable using DNS lookup tools and that DNS propagation has completed. If using Cloudflare, ensure the records are configured as DNS Only and not Proxied. After validating the records, run Check Status again in BoldDesk.
Email notifications are not being received Verify that DKIM validation has completed successfully, confirm the CNAME records resolve to the expected target values, check for duplicated domain names in the DNS records, and review any mail gateway, spam filtering, or email security policies that may be blocking incoming messages.
Verification still fails after correcting records If the records were previously created incorrectly, delete the invalid record and create a new CNAME record using the correct hostname and target value. Wait for DNS propagation and then run Check Status again. Some DNS providers apply updates more reliably when records are recreated rather than modified.

Before recreating DKIM records, verify that the BoldDesk-generated CNAME values exactly match the published DNS records, there are no duplicate or conflicting entries, and DNS propagation has completed. In many cases, verification and email delivery issues are caused by hostname formatting errors, conflicting DNS records, or incomplete propagation rather than invalid DKIM records.

Frequently Asked Questions

  1. Where do administrators configure DKIM in BoldDesk?
    Go to Admin > Emails > DKIM Settings.

  2. Why don’t any domains appear on the DKIM Settings page?
    Domains appear only when custom support email addresses are configured in your BoldDesk account.

  3. Can I configure DKIM for Gmail or Yahoo email addresses?
    No. DKIM can only be configured for domains that your organization owns and manages.

  4. How long does DKIM verification take after adding DNS records?
    DNS updates can take up to 72 hours to propagate. Verification can succeed only after DNS records are visible publicly.

  5. Why does DKIM verification fail even after adding the CNAME record?
    A common cause is that the DNS provider auto-appends the domain. In that case, the DKIM record name is entered incorrectly (for example, including .example.com when the provider already adds it).

  6. Can DKIM be configured for BoldDesk default bolddesk.com support emails?
    No. DKIM is already configured for BoldDesk default support email addresses ending in bolddesk.com, and additional configuration is not available from the DKIM Settings page.

  7. Can DKIM CNAME records be created at the root domain?
    BoldDesk indicates CNAME records should not be used for root domains, only subdomains.

  8. Can multiple CNAME records be added to the same subdomain for DKIM?
    BoldDesk indicates you can have only one CNAME record per subdomain.

  9. Why does DKIM verification fail in SiteGround, GoDaddy, cPanel, or other DNS providers?
    Many DNS providers automatically append the domain name to the host field. If you enter the full domain manually, the resulting record may become malformed and fail DKIM validation.
    Always verify how your DNS provider stores and displays the record after creating it.

Related Articles

  1. Secure Your Email Domain with DMARC: Enhancing Email Security
  2. Fix Custom Domain Issues in BoldDesk Using a CNAME Record
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Comments (0)
Access denied
Access denied
Access denied
Access denied

No articles or sections found
No articles or sections found