• 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!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. A

    Resolved [DigitalOcean DNS extension] TTL values not synchronized

    Thank you!
  2. A

    Resolved [DigitalOcean DNS extension] TTL values not synchronized

    In two cases, when I added a new record and when I tried to edit it, in both cases the value that report DigitalOcean was 86400 TTL. I have to mention that in Plesk it appear the value that I created 3600, so the edit was delete this value, write it again and apply. Steps: Go to domains >...
  3. A

    Resolved [DigitalOcean DNS extension] TTL values not synchronized

    At the time still happening on Plesk Obsidian Version 18.0.35 Update #2. Is it normal or has the bug been fixed?
Back
Top