• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Bug report: Plesk changes zonefile when editing username/password

Tozz

Regular Pleskian
---------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk, 10.4.4 Update 20, Ubuntu Lucid, AMD64

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
If DNS zone is changed so website is hosted on another IP, but mail is still running on Plesk and user changes his username and/or password, IP of the mail. DNS record is changed to the IP the siteis hosted on.

e.g.: Create hosting subscription for example.com on a Plesk machine with IP 10.0.0.1 (for the example)

- Change 'example.com' A-record to 192.168.0.1 (site is hosted elsewhere)
- Change 'www.example.com' A-record to 192.168.0.1 (site is hosted elsewhere)
- Keep the mail.example.com' to the default, beeing 10.0.0.1 (mail is hosted on the plesk server)
- Change your subscription password and/or username

ACTUAL RESULT
- mail.example.com A-record is changed to 192.168.0.1. As 192.168.0.1 is not configured to receive mail for this domain, mail is rejected and lost.

EXPECTED RESULT
- Plesk should not reset manually edited zonefiles.
- Plesk should keep 'mail.example.com' pointing to 10.0.0.1
- Plesk should never change DNS zone data whatsoever when changing something trivial as an FTP password
 
Back
Top