• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs DNS CNAME invalid when pointing to _domainkey

Michiel Klaver

New Pleskian
TITLE:
DNS CNAME invalid when pointing to _domainkey
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx 17.5 Linux
PROBLEM DESCRIPTION:
When creating a CNAME DNS record pointing to Microsoft Office365 for DKIM, Plesk generates an error indicating the content of the record is invalid. It seems not to like the underscore _ character. I followed the official manual to the letter [1].

According to the relevant RFCs, this should be valid [2].

[1] Manually hooking up DKIM signing in Office 365
[2] Underscores in DNS
STEPS TO REPRODUCE:
Create a new CNAME DNS record, point it to a valid host containing an underscore, for example:
selector1-contoso-com._domainkey.contoso.onmicrosoft.com​
ACTUAL RESULT:
Plesk generates an error, stating I entered an invalid DNS record.​
EXPECTED RESULT:
I expect Plesk to follow RFC and accept this input as valid DNS.​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Back
Top