• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue dkim=neutral reason="invalid (public key: not available)"

Edinho

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian 18.0.64 Update #1 Web Host Edition
Hi guys,
I have a problem that is driving me crazy.
I have a domain that I can't get the DKIM record validated in any way, for all my other domains I managed, but this one I just can't. I have the DNS zone on OVH that takes the key obtained from the plesk configuration, I also checked in the DNS records of plesk if all three were the same. But every time I try to check the record I always get the same problem: dkim=neutral reason="invalid (public key: not available)"

Could it be because this domain is the only one with a slightly more peculiar extension being a .store? Otherwise I cannot understand why all the other domains the DKIM works and this one does not.
Thanks to all
 
Back
Top