Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Existing DNS Check Fails on Exchange 2016 CU 23 with DKIM Signer version 3.4.0 #375

Open
mvanbeuren opened this issue Jan 9, 2023 · 0 comments

Comments

@mvanbeuren
Copy link

Versions

  • Windows Server 2016
  • Exchange 2016 CU 23
  • 3.4.0

Description

DKIM signer installs successfully but when configuring "Domain Settings", the "existing DNS" check fails regardless of whether the "Direct NS Check" box is marked or not. (Will this cause issues with DKIM signing even if DKIM checkers such as DMARCian and MXToolbox see the record?)

Steps to Reproduce

  1. Install DKIM signer
  2. Begin configuration and proceed to "Domain Settings" page
  3. Add domain and generate new key for domain
  4. Click "Check" button for "Existing DNS" up to 3 days after changes made to external DNS to allow propagation

Expected behavior: Box auto-fills with matching "Suggested DNS record".

Actual behavior: Box says "no found for example._domainkey.domain.net" regardless of whether the "Direct NS check" box is marked or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant