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

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