• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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