• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

DNS defaults ignored - Plesk 8.01

madsere

Regular Pleskian
Cudos to the development team for finally making it possible to migrate Ensim sites to Plesk with the migration wizard of Plesk 8.01 (Virtuozzo/RHEL4). This will greatly enhance our chances of finally phasing out Ensim and concentrate on Plesk.

There is however still one serious problem I would like to address and if possible, have a fix for:

The " dns defaults" - mainly the change from the default ns.< domain> to ns1.ourdns.com and ns2.ourdns.com - seem to be ignored both by the domain migration wizard, by domain aliases and by group operations.

In all cases Plesk reverts to using the " standard" Plesk ns.< domain> setting for NS records instead of the changes made under server > dns.

The only way to correct this seem to be to go into each domain > dns > default. When you migrate hundredes of domains that is both tedious and time consuming.

For domain aliases the template changes are completely ignored, also when reset (default clicked).
 
Yep, I've got the same problem, not been able to find a solution.

It's a real problem when using domain aliasing.
 
Back
Top