[GH-ISSUE #143] Could not extract public key from dns record #110

Closed
opened 2026-02-26 10:35:59 +03:00 by kerem · 10 comments
Owner

Originally created by @spid3r1987 on GitHub (Mar 4, 2016).
Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/143

Help!!
i have installed the DKIM-Exchange via the online installer.
configured everything, but getting the error of could not extract public key from dns record.

i have noticed that there is the issue fix, but i do not have the files mentioned on my server to edit the file.

how can i resolve this issue?

Regards
michael

Originally created by @spid3r1987 on GitHub (Mar 4, 2016). Original GitHub issue: https://github.com/Pro/dkim-exchange/issues/143 Help!! i have installed the DKIM-Exchange via the online installer. configured everything, but getting the error of could not extract public key from dns record. i have noticed that there is the issue fix, but i do not have the files mentioned on my server to edit the file. how can i resolve this issue? Regards michael
kerem 2026-02-26 10:35:59 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@Pro commented on GitHub (Mar 4, 2016):

Which version did you install?

Can you post the content of the two text fields "suggested DNS record" and "existing DNS record"?

<!-- gh-comment-id:192280303 --> @Pro commented on GitHub (Mar 4, 2016): Which version did you install? Can you post the content of the two text fields "suggested DNS record" and "existing DNS record"?
Author
Owner

@spid3r1987 commented on GitHub (Mar 4, 2016):

Version is 3.0.2
suggested has
"v=DKIM1; k=rsa; p=KEY REMOVED"
existing has nothing then below says could not extract public key from dns record

<!-- gh-comment-id:192289058 --> @spid3r1987 commented on GitHub (Mar 4, 2016): Version is 3.0.2 suggested has "v=DKIM1; k=rsa; p=KEY REMOVED" existing has nothing then below says could not extract public key from dns record
Author
Owner

@Pro commented on GitHub (Mar 4, 2016):

Note: You don't need to remove the public key, since it will be publicly visible anyway.
Did you setup you DNS record correctly? Did you press the "check DNS" button?

<!-- gh-comment-id:192294751 --> @Pro commented on GitHub (Mar 4, 2016): Note: You don't need to remove the public key, since it will be publicly visible anyway. Did you setup you DNS record correctly? Did you press the "check DNS" button?
Author
Owner

@spid3r1987 commented on GitHub (Mar 4, 2016):

ahh right ok lol.
suggested :
"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmw0KIrvuofz5rC6moCHB21Y9ucwtVPLKtEn8FNraJ70X3IpvXQgonwJg/MpNobtbmIjFuBJ231/FkgVfGv284c8TSuWnqKmJ0T5YibZIX9qrSnMALwyj9clMkD2jt6gcgeGH+59BkeN44sn1RCNWqe4DDWJukfB2wh1GkzA1HQiaChdHXntizps7P5IIoJdWgn5b0a0608LoNRfgg8r8zjXsQ115mZR9kALPcHuiLTV3iD+TjhttQGn4z3xdB5FnsqIkHbWXvygX71q8JjeGMO0wtKCSkXNUTQb3dVMAF8CzpXbWmhV1dEc94lh/E8TcyfeQDeFq4Gz+/8upfzvQzwIDAQAB"

Existing dns:
"blank"
could not extract public key in red at the bottom after pressing the check dns button

opened DNS management on server, rightclicked domain, add other > txt > entered the suggested dns name - domain name. then entered the key etc into the txt box.

but when i check the record, nothing is stored in the txt field...

<!-- gh-comment-id:192296909 --> @spid3r1987 commented on GitHub (Mar 4, 2016): ahh right ok lol. suggested : "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmw0KIrvuofz5rC6moCHB21Y9ucwtVPLKtEn8FNraJ70X3IpvXQgonwJg/MpNobtbmIjFuBJ231/FkgVfGv284c8TSuWnqKmJ0T5YibZIX9qrSnMALwyj9clMkD2jt6gcgeGH+59BkeN44sn1RCNWqe4DDWJukfB2wh1GkzA1HQiaChdHXntizps7P5IIoJdWgn5b0a0608LoNRfgg8r8zjXsQ115mZR9kALPcHuiLTV3iD+TjhttQGn4z3xdB5FnsqIkHbWXvygX71q8JjeGMO0wtKCSkXNUTQb3dVMAF8CzpXbWmhV1dEc94lh/E8TcyfeQDeFq4Gz+/8upfzvQzwIDAQAB" Existing dns: "blank" could not extract public key in red at the bottom after pressing the check dns button opened DNS management on server, rightclicked domain, add other > txt > entered the suggested dns name - domain name. then entered the key etc into the txt box. but when i check the record, nothing is stored in the txt field...
Author
Owner

@Pro commented on GitHub (Mar 4, 2016):

Please check you DNS record with a tool like http://www.protodave.com/tools/dkim-key-checker/ or Google for another checking tool

<!-- gh-comment-id:192303949 --> @Pro commented on GitHub (Mar 4, 2016): Please check you DNS record with a tool like http://www.protodave.com/tools/dkim-key-checker/ or Google for another checking tool
Author
Owner

@spid3r1987 commented on GitHub (Mar 4, 2016):

not showing any dns txt record found.... strange

<!-- gh-comment-id:192326869 --> @spid3r1987 commented on GitHub (Mar 4, 2016): not showing any dns txt record found.... strange
Author
Owner

@Pro commented on GitHub (Mar 4, 2016):

Make sure you set up the DNS correctly. Then DKIM Signer will find the record.

<!-- gh-comment-id:192327647 --> @Pro commented on GitHub (Mar 4, 2016): Make sure you set up the DNS correctly. Then DKIM Signer will find the record.
Author
Owner

@spid3r1987 commented on GitHub (Mar 4, 2016):

Never mind. Found a different tool and it's all sorted now mate. Thanks anyway

Sent from my Samsung device

-------- Original message --------
From: Stefan Profanter notifications@github.com
Date: 04/03/2016 14:35 (GMT+00:00)
To: Pro/dkim-exchange dkim-exchange@noreply.github.com
Cc: technicalteam technicalteam@prservicesyorkshire.co.uk
Subject: Re: [dkim-exchange] Could not extract public key from dns record (#143)

Please check you DNS record with a tool like http://www.protodave.com/tools/dkim-key-checker/ or Google for another checking tool


Reply to this email directly or view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/143#issuecomment-192303949.

<!-- gh-comment-id:192357663 --> @spid3r1987 commented on GitHub (Mar 4, 2016): Never mind. Found a different tool and it's all sorted now mate. Thanks anyway Sent from my Samsung device -------- Original message -------- From: Stefan Profanter notifications@github.com Date: 04/03/2016 14:35 (GMT+00:00) To: Pro/dkim-exchange dkim-exchange@noreply.github.com Cc: technicalteam technicalteam@prservicesyorkshire.co.uk Subject: Re: [dkim-exchange] Could not extract public key from dns record (#143) Please check you DNS record with a tool like http://www.protodave.com/tools/dkim-key-checker/ or Google for another checking tool — Reply to this email directly or view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/143#issuecomment-192303949.
Author
Owner

@luckman212 commented on GitHub (Mar 4, 2016):

Could be that you are using split DNS and only set the DKIM record on your public facing DNS (eg Network Solutions, GoDaddy etc) and forgot to add it to the internal side? I saw that myself. It is harmless anyway.

<!-- gh-comment-id:192369129 --> @luckman212 commented on GitHub (Mar 4, 2016): Could be that you are using split DNS and only set the DKIM record on your public facing DNS (eg Network Solutions, GoDaddy etc) and forgot to add it to the internal side? I saw that myself. It is harmless anyway.
Author
Owner

@spid3r1987 commented on GitHub (Mar 4, 2016):

I set the records on my hosted dedicated server which controls various domains. And on my local sbs server to cover both angles incase it was looking at the hosted dedicated server rather than local server.

Sent from my Samsung device

-------- Original message --------
From: lukehamburg notifications@github.com
Date: 04/03/2016 17:27 (GMT+00:00)
To: Pro/dkim-exchange dkim-exchange@noreply.github.com
Cc: technicalteam technicalteam@prservicesyorkshire.co.uk
Subject: Re: [dkim-exchange] Could not extract public key from dns record (#143)

Could be that you are using split DNS and only set the DKIM record on your public facing DNS (eg Network Solutions, GoDaddy etc) and forgot to add it to the internal side? I saw that myself. It is harmless anyway.


Reply to this email directly or view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/143#issuecomment-192369129.

<!-- gh-comment-id:192378026 --> @spid3r1987 commented on GitHub (Mar 4, 2016): I set the records on my hosted dedicated server which controls various domains. And on my local sbs server to cover both angles incase it was looking at the hosted dedicated server rather than local server. Sent from my Samsung device -------- Original message -------- From: lukehamburg notifications@github.com Date: 04/03/2016 17:27 (GMT+00:00) To: Pro/dkim-exchange dkim-exchange@noreply.github.com Cc: technicalteam technicalteam@prservicesyorkshire.co.uk Subject: Re: [dkim-exchange] Could not extract public key from dns record (#143) Could be that you are using split DNS and only set the DKIM record on your public facing DNS (eg Network Solutions, GoDaddy etc) and forgot to add it to the internal side? I saw that myself. It is harmless anyway. — Reply to this email directly or view it on GitHubhttps://github.com/Pro/dkim-exchange/issues/143#issuecomment-192369129.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dkim-exchange-Pro#110
No description provided.