• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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