Forwarded to devs Plesk Obsidian: Mail handling for subdomains not fully implemented regarding DNS (MX, DKIM)?

[B_P]

User name: B_P

TITLE

Plesk Obsidian: Mail handling for subdomains not fully implemented regarding DNS (MX, DKIM)?

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian (Web Pro), Version 18.0.27
Ubuntu 16.04.6 LTS

PROBLEM DESCRIPTION

Since Obsidian, Plesk should be able to handle mails for sudomain mail accounts ([email protected]) as well.

It looks as if the DNS configurations for these subdomain cases are not yet fully implemented:

a) When enabling a subdomain for mail submission, Plesk does not create a separate MX record for this subdomain.
b) When enabling DKIM for this subdomain, the corresponding DKIM resource record is not added to the DNS settings.
c) When disabling DKIM for this subdomain, the corresponding (manually created DKIM RR,  How to get the DKIM public key from Plesk if DNS is not installed?) will not be deleted from the DNS settings.

STEPS TO REPRODUCE

1. Create a subdomain for the main domain of a subscription
2. Enable mail services for this subdomain and
3. Enable DKIM signing for this subdomain
4. Disable DKIM signing
5. Disable mail service for subdomain

ACTUAL RESULT

• Mail submission works in general, however:
• No MX record can be found for the subdomain in the DNS settings (after step 2)
• no TXT record for the DKIM key can be found for the subdomain (after step 3)
• the DKIM TXT RR for the subdomain is not deleted (after step 4)
• the (manually) create MX record for the subdomain will not be deleted (after step 5)

EXPECTED RESULT

• A MX record is included for the subdomain when mail services are active
• A TXT record (DKIM) is added and removed for the subdomain if DKIM is enabled/disabled

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[obendev]

Can confirm. When creating a subdomain, enabling mail service and enabling dkim, no dkim records, nor mx record is added to the DNS zone of the main domain.

 

[IgorG]

From developer:

By default subdomains created without own DNS zone. Since there is no DNS zone for subdomain, record for DKIM is not created. Customer should first enable own DNS zone for subdomain then switch on DKIM for subdomain mail service.
So the correct steps would be:

• create subdomain
• go to subdomain page -> DNS settings
• click 'Enable'
• go to subdomain page -> Mail settings
• check 'Activate mail service on this domain'
• check 'Use DKIM spam protection system to sign outgoing email messages'
• apply/save changes

 

[B_P]

From developer:

By default subdomains created without own DNS zone. Since there is no DNS zone for subdomain, record for DKIM is not created. Customer should first enable own DNS zone for subdomain then switch on DKIM for subdomain mail service.
So the correct steps would be:

• create subdomain
• go to subdomain page -> DNS settings
• click 'Enable'
• go to subdomain page -> Mail settings
• check 'Activate mail service on this domain'
• check 'Use DKIM spam protection system to sign outgoing email messages'
• apply/save changes

@IgorG As the parent zone contains all data about the sub(sub...)domains in case the "own subdomain zone" is not enable, why aren't just the corresponding records just added to the main domain zone then? This seems to be inconsistent and feels a bit as if this is just a matter of not being implemented so far?

 

[PAWLO]

Can confirm. When creating a subdomain, enabling mail service and enabling dkim, no dkim records, nor mx record is added to the DNS zone of the main domain. Kodi nox

 

[andrij]

issue still exists.