dkim-exchange icon indicating copy to clipboard operation
dkim-exchange copied to clipboard

Published 20 hours ago • verified publisher icon Pro

DKIM "Existing DNS" Check fails even though I can manually verify

Open MrDecepticon opened this issue 3 years ago • 6 comments

Versions

  • Windows Server Version: Server 2019
  • Exchange Version: 15.2.792.3
  • Installed DKIM Exchange Version: 3.3.2

Description

I set this up a while back (a couple years) and have not had any issues since then until now. I allowed the DKIM Singer to update itself and on a whim I wanted to verify the DNS record. Before I did not have any issues with this but now the Check to run on the Domain Settings tab fails every time. I immediately went to my DNS provider and manually verified the keys match. Also, verified via MXToolbox to make sure I wasn't losing my mind.

Checker continuously states that there is no record found.

Steps to Reproduce

  1. Click the Check button under Domain Settings
  2. wait for verification

Expected behavior: DNS Records to be found

Actual behavior: States no record found for my key even though I can manually verify.

MrDecepticon avatar Sep 07 '21 14:09 MrDecepticon

On the "Domain Settings" tab, have you tried with "Direct NS" both checked and unchecked. That was added a few releases ago as a lot of people were getting failures due to the existing lookup method.

DJBenson avatar Sep 07 '21 14:09 DJBenson

I do not see this checkbox on the Domain Settings tab. DKIM Signer shows that 3.3.2 is in stalled but on the about page it shows 3.2.6. Could that be why I don't see this option?

MrDecepticon avatar Sep 09 '21 11:09 MrDecepticon

Ok, I'm not very smart. Apparently I have been running the wrong version that I had sitting in another location.

MrDecepticon avatar Sep 09 '21 11:09 MrDecepticon

Didn't mean to close. It still fails the check regardless if that box is checked or not.

MrDecepticon avatar Sep 09 '21 11:09 MrDecepticon

Would like to add that I installed this on one of my 4 exchange servers. 2 of them in my DR facility where i deployed it first were able to check the DNS record with the Direct NS Check while the PROD side Exchange servers were not but i was able to check the DNS record with the Direct NS Check box UNCHECKED. go figure. possibly DNS is being blocked on my Firewalls on one side and not the other. If i can confirm that i will let you all know.

carlitosgomes12 avatar Nov 11 '21 23:11 carlitosgomes12

My DNS was being blocked on the firewall on one side and not the other.

carlitosgomes12 avatar Nov 12 '21 00:11 carlitosgomes12