• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

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