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

Plesk Migration DNS Error

Kanagaraj

Basic Pleskian
Hi,
We some of qustions,

We are migration to old plesk server to our new plesh server, after migrating some of domains are working in new server and some of domains are not working, the page goes apache test page. Our Primary name server ip is New server and Secondary name server ip is Old server ip. Now both Server is Online and working

What is the proper way to Migration the servers

Our new server CentOs 4 with Plesk7.5.4
Our Old server Rh 9 With Plesk7.5.4

Regards
Kanagaraj
 
Originally posted by Kanagaraj
Hi,
We some of qustions,

We are migration to old plesk server to our new plesh server, after migrating some of domains are working in new server and some of domains are not working, the page goes apache test page. Our Primary name server ip is New server and Secondary name server ip is Old server ip. Now both Server is Online and working

What is the proper way to Migration the servers

Our new server CentOs 4 with Plesk7.5.4
Our Old server Rh 9 With Plesk7.5.4

Regards
Kanagaraj

I've got similar issue: remove leftovers of default skeleton from the migrated domains: Plesk mor**s copy migrated content over skeleton one.
 
Back
Top