• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Serverwide DNS Mode Change

S

Simber

Guest
Hi,

I am in the process of upgrading our webserver & need to change the dns mode on one of the servers to slave/secondardy for all domains, Is it possible to do this on mass or is it a case of doing all individually?

Im using server 2008, plesk 10.2.0 on both.

basicly I currently have 3 servers.

1 which is dieing which is currently the primary server
the second has an out of date dns list / zones,

& the third is a new build with new correct dns.

What i want to do is set the second server as a slave to the third, so that eventually the first can be removed this will give me some breathing space incase the first one dies as the new build is currently not listed as a name server for any of the domains.

Using this method i can still have the dns resolving correctly from a known good copy for as long as i need & dont have to worry about replication time when i do the final cut over.

PS i should have mentioned the dns is flaky / corrupt on the primary thats the reason im not just migrating.


Hope this makes sense.
 
Back
Top