• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved Digital Ocean DNS extension doesn't sync MX records TTL

TomBoB

Silver Pleskian
Username:

TITLE

Digital Ocean DNS extension doesn't sync MX records TTL

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.54 Update #3, AlmaLinux 8.8

PROBLEM DESCRIPTION

Changes of the TTL of an MX record is not being synched via the Digital Ocean DNS extension. Instead they are all reset to default 86400.

STEPS TO REPRODUCE

Use Digital Ocean DNS extension to sync domains DNS data to Digital Ocean name server.
Change the TTL of an MX entry.

ACTUAL RESULT

is being set to 86400 on Digital Ocean name server.

EXPECTED RESULT

is being set to the TTL specified in Plesks domain DNS settings

ANY ADDITIONAL INFORMATION

tested with a clients MX records set to use the gmail mail servers.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for reporting this. The issue with the extension is already known and will be fixed in a future update of the extension. It can be traced in the changelog as EXTPLESK-2272 once that becomes available.
 
Hi! I am glad to say that the issue is fixed in the DigitalOcean DNS extension since 1.4.0 version,

Changes, 1.4.0 (1 November 2023)
  • [-] Custom TTL values for individual records are now correctly synchronized with the DigitalOcean DNS service. (EXTPLESK-2272)

Let me know if you have any feedback regarding the "synchronization of TTL per record" issue.
 
Back
Top