• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Long DNS records ignored by Microsoft DNS

What DNS software do you use with Plesk Onyx for Windows?

  • BIND DNS Server

    Votes: 0 0.0%
  • Simple DNS Plus

    Votes: 0 0.0%
  • None

    Votes: 0 0.0%

  • Total voters
    1
  • Poll closed .

Paul Hermans

Basic Pleskian
We have several Windows Servers 2012R2 and Windows Server 2016 with Plesk Onyx and Microsoft DNS.

When we add for example 2048 bits DKIM DNS record which is a very long record, this record is completely ignored by Microsoft DNS.

Is this a known issue or a bug in Plesk?


EDIT:

When I add the same new very long TXT record directly to Microsoft DNS (via Remote Desktop) the value is accepted and working.
 
Last edited:
Thanks Igor, that seems the problem! Thanks for pointing this out to me.

Can you please ask the developers to fix this? It is a real problem for us to implement DKIM email signing.
 
Back
Top