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

DNS fix?

What's the ETA on that?

The discoverer will be publishing the vulnerability August 2nd. We have to be able to test the Plesk patch and fix the issues that are inevitably going to be caused by the Plesk update before the DNS poisoning from these is in the wild - which is going to be around August 3rd (if not sooner).
 
Greetings:

See http://www.theregister.co.uk/2008/07/09/dns_bug_student_discovery/

This vulnerability was reported approximately three years ago.

If your servers are secured, and your DNS servers secured (which means you only transfer between your own name severs, and only recursive queries through your own servers), then the DNS poisoning to worry about is not your own cluster, those servers external to yours.

That's why all parties need to patch. If it was just Plesk users who patched or just H-Sphere users who patched, the threat would still be present from the outside world.

In any event, we are all waiting on patching -- Plesk, H-Sphere, and other Parallels products as every patched server contributes to the overall health of the net.

Thank you.
 
Back
Top