• 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.

Question MX Records for Domains on a Plesk Server

toptronix

New Pleskian
Hi,

I would like to ask if someone can help me to answer the following question:
What is the best practice to set the mx record for all the domains hosted on the same plesk server.

For example:
Plesk server Host: mail.example.com
Reverse DNS Record: mail.example.com
The Domains hosted on this server: domain1.com, domain2.com, domain3.com, etc.

Is it now recommended looking at blacklisting and general mail policies
That we set for all the domains mail.example.com as MX record instead of mail.domain1.com, mail.domain2.com, mail.domain3.com, etc?
mail.domain1.com, mail.domain2.com, mail.domain3.com is the default configuration generated by plesk.

Thanks
Regards
Chris
 
Back
Top