DKIM Selector Not Found: How To Fix the DNS Side

December 31, 2025 • InboxGreenEmail Team

🚨 DKIM issues can silently kill replies.

If opens dropped, replies disappeared, or bounces increased, treat it as an incident. Run the scan and get a fix path.

No signup required. Works on any domain.

DKIM Selector Not Found: How To Fix the DNS Side

When you send an email, you want it to land in the inbox, not the spam folder. One common issue that can prevent this is a DKIM selector not being found. This can lead to failed email authentication, which affects your domain reputation and ultimately your inbox placement. If you see warnings in Gmail or receive bounced emails, it becomes urgent to address this. In this article, we will walk through how to diagnose and fix the DKIM selector issue from the DNS side.

At a glance

  • This problem affects SaaS founders, marketers, and technical teams managing email sending.
  • This article will help you understand how to check and fix DKIM selector issues.
  • By following these steps, you can improve your email deliverability and domain reputation.

When this problem shows up in real life

Imagine you are sending out an important marketing email, and you notice that a significant number of recipients report not receiving it. You check your logs and find entries like:

DKIM verification failed for [email protected]: selector not found

Or perhaps you see in Gmail headers:

Authentication-Results: mx.google.com; dkim=fail (bad signature) [email protected]

These messages indicate that the DKIM selector is either missing or misconfigured. You might also receive support tickets from users stating that they are not receiving emails, which can be traced back to this DKIM issue.

Step by step: DKIM setup

  1. Identify your DKIM selector.

    Your DKIM selector is a string that helps identify the public key in your DNS records. It is often set when you configure your email service. Common examples include "default" or "email". Check your email service documentation for the exact selector.

  2. Check your DNS records.

    Use a DNS lookup tool to check if the DKIM record exists. You can use the following command in your terminal:

    dig TXT selector._domainkey.example.com

    Replace "selector" with your actual DKIM selector and "example.com" with your domain.

  3. Update or add the DKIM record.

    If the record is missing, you need to create it. Here is an example of what a DKIM record might look like:

    selector._domainkey.example.com. IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB..."

    Make sure to replace "selector" with your DKIM selector and "p=" with your actual public key.

  4. Verify the changes.

    After updating your DNS records, wait for DNS propagation (this can take a few minutes to 48 hours). Then, re-run the DNS lookup command to ensure the record is now present.

  5. Test your DKIM setup.

    Send a test email to a service like Mail Tester or check the headers with the Email Header Analyzer to confirm that DKIM is passing.

Common mistakes

  • Missing DKIM record.

    Symptom: Emails fail DKIM verification.
    Cause: The DKIM record has not been added to DNS.
    Fix: Create the DKIM record in your DNS settings.

  • Incorrect selector.

    Symptom: DKIM fails with "selector not found".
    Cause: The selector used in the email does not match the one in DNS.
    Fix: Ensure the selector in your email matches the DNS record.

  • Propagation delays.

    Symptom: Changes are not reflected immediately.
    Cause: DNS changes can take time to propagate.
    Fix: Wait for up to 48 hours and check again.

  • Incorrect public key format.

    Symptom: DKIM verification fails with "bad signature".
    Cause: The public key in the DKIM record is malformed.
    Fix: Double-check the public key format and ensure it is correctly entered in the DNS record.

Troubleshooting when it still fails

  • DKIM fails but record exists.

    Symptom: DKIM still fails after confirming the record is present.
    Likely cause: The key may be incorrect or not matching.
    What to try next: Verify the public key against your email service settings.

  • Authentication-Results headers indicate failure.

    Symptom: Headers show DKIM=fail.
    Likely cause: The email was sent from a different server than expected.
    What to try next: Ensure the sending server is authorized in your SPF record.

  • Emails still go to spam.

    Symptom: Emails are delivered but land in the spam folder.
    Likely cause: Other factors are affecting deliverability.
    What to try next: Check your domain reputation and consider running a InboxGreen checker.

Related checks you should run

  • SPF, DKIM, DMARC alignment.
  • DNS TTL and propagation delays.
  • Domain reputation, bounces, spam reports.
  • List quality and engagement patterns.

FAQ

Why is DKIM still failing on my email service after I added the record?

This can happen if the selector in your email headers does not match the one in your DNS record. Double-check that both match exactly, including case sensitivity.

How long do DNS changes take to apply on my provider?

DNS changes can take anywhere from a few minutes to 48 hours to propagate fully. It often depends on your DNS provider and the TTL settings.

Can I use more than one DKIM selector with this setup?

Yes, you can have multiple DKIM selectors for different applications or services. Just ensure each selector has its own corresponding DNS record.

How do I know if my DKIM record is correctly formatted?

You can use a DKIM checker tool to validate the formatting of your DKIM record. The DKIM Checker can help you with this.

What to do next

Now that you have a better understanding of how to fix the DKIM selector not found issue, take action. Start by checking your DNS records and confirming that your DKIM selector is correctly configured. Use the InboxGreen checker to test your setup and ensure everything is working as it should. If you encounter any issues, refer back to this guide for troubleshooting tips.


Free Deliverability Scan

Check SPF, DKIM, DMARC and List-Unsubscribe for your domain in seconds.