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

Issue Plesk Email Overwriting Gmail MX records

jasonbunnell

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk 18.0.64
I am hosting on DigitalOcean with Ubuntu 22.04 and Plesk Obsidian 18.0.64. All the domain are using DigitalOcean nameservers. I have one site that is pulled from a GitHub repo. Not sure why that would matter, but it seems every time I pull updates it screws up the email MX records on DigitalOcean.

This business uses Google Suite for email, etc. DigitalOcean has a one click button to add Gmail MX records. It seems periodically Plesk will update those thereby causing problems with email service.

QUESTION: is there a setting so that Plesk will not change MX records on DigitalOcean for email?

I have tried going to Mail Settings for the domain and selecting Not Configured for Mail Service on this domain. There is a checkbox that is checked for Enable mail autodiscover.

The problem seems to be DNS Settings. If I correct the MX records on DigitalOcean, Plesk will overwrite the correct settings.
 
I assume you're using the DigitalOcean DNS extension in Plesk to sync your domains DNS zones to DO, is that right?

In this case, any changes made the DNS zone directly at DigitalOcean will be overwritten by the DNS zone from Plesk. As the synchronization replaces the DNS zone whenever any domain changes (related the DNS zone) have been made in Plesk. Hence you'll have to make any DNS changes in Plesk (instead of directly at DigitalOcean). Alternatively you can disable the DigitalOcean DNS extension, but that will stop DNS synchronization for all domains.
 
Back
Top