• 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 9.5.1 issue with MS-DNS

A

AriaF

Guest
Hello,

I'm having issues with Plesk 9.5.1 on windows 2008 R2 x64 !

Windows 2008 R2 has DNS 6.0 built-in and I will have to either go with BIND or MS-DNS !

The thing is, plesk is definitely not compatible with MS-DNS 6.0 (either on Plesk 9.3) and that's why I can't see the actual zone files in c:\windows\system32\dns path.

Lets say we are going to migrate a larg number of websites from a windows 2003 server to a windows 2008 R2 and it cannot be done over a night and will need more time.

If we use MS-DNS (since we have to move the zone files after each website migration to forward A records to new server) and the customer try to add a new domain on the new server, will get an error in regards to DNS service error !

It has a fix in parallels KB but after doing that, adding domains will work without problem but you won't be able to see the actual zone files in the above path.

My question here:

1. when will plesk going to support MS-DNS 6.0 ?
2. in my situation, what would be the best way of doing the migration ?

Any help would be appreciated.

Thank you all.
 
Back
Top