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

DNS problem after restore

R

RichardD

Guest
Hi to all,

To replace the old Plesk server with a new one, and keep the original hostname/ip we did the following:

We made a full backup of the Plesk 10.1.1 data from a virtual machine SLED 10.3 and moved a local copy
to a new virtual machine OpenSuse 11.4 Plesk 10.2 and peformed a full restore.

There were only a few client errors but our main problem was that we could't connect to the CP by host name (same as the old server) internal ip worked fine.
We found a forum post solution, for OpenSuse 11.4 with this problem, to unmark IP_Listening 172.0.0.1. in named.conf,
which didn't work.

The reason why we didn't use the migration tool from the panel is that we couldn't find any manual or knowledgebase articles for our situation, two different OS en Plesk versions.

So the question is can we succsesfully perform a migration between the OS and Plesk versions
and where to look in Plesk (our knowledge of Linux is sufficient) if we come across the same DNS problems.

Thanks,
Richard
 
Back
Top