1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

IP Change of secondary DNS

Discussion in 'Plesk Expand 2.2 General Discussion' started by loopback-martin, Oct 16, 2007.

  1. loopback-martin

    loopback-martin Guest

    Hi all.

    We are about to move our secondary DNS to a new server and location which forces us to change the IP as well.

    Is there a way to change the IP of the secondary DNS Server in expand, without removing the DNS Server object and then add it again? Is there a 'preferred' way to do it?

    We are using CDNS in 'slave' mode.

    Thanks all.
  2. girin

    girin Guest


    You can change the IP of your CDNS server from Expand CP.
    Just go to Centralized DNS > DNS Server #xxxx and click Change Connection Parameters button. Then enter a new IP and press ok. The ip and hostname of the CDNS server will be changed, the DNS templates and NS records will be changhed on Plesk servers too.

    But I should warn you, if you will perform this operation then

    on your Plesk for UNIX servers you will have:
    - extra ACL record with old IP (you can manually remove it from Plesk CP).

    on your Plesk for WINDOWS servers you will have:
    - extra record with old IP in Zone Transfers Template (you can remove it from Plesk CP)
    - extra record with old IP in Zone Transfers for each domain of the server.
  3. girin

    girin Guest

    And another thing, why are you so afraid to remove the CDNS from you system and then add a new one?
    You are using CDNS in slave mode and so remove/add of CDNS will be safe for your domains resolving.
  4. loopback-martin

    loopback-martin Guest

    Hmm, my bad. We are still using 2.1.3, and the connection parameter icon must be new in 2.2.x.

    The reason for posting is that with all the issues Expand has had in the past, especially with the DNS part, I would like to hear from SwSoft if there's a preferreed way.

    Now it seems that the 2.2-release will solve this by adding the option to change IP.

    Thanks for the reply.

  5. Sergey L

    Sergey L Golden Pleskian Staff Member

    Aug 10, 2006
    Likes Received:
    We think that removing and adding slave CDNS server back in 2.1.3 is quite safe and fast operation. We often applied it when repairing Expand after some DNS server misconfiguration. So it is quite common practice. You can ask other users about their experience if you are unsure.

    Also you can probably ask people what they think about our 2.2.1 patch. 2.2.0 was buggy in DNS and upgrade aspects due to we complete remade CDNS implementation. But since 2.2.1 is released the amount of claims we receive was drastically reduced. Probably it is a good option to upgrade to 2.2.1 and get all its benefits.
  6. loopback-martin

    loopback-martin Guest

    Thanks for your reply 'Expand'

    We will most likely do an upgrade to 2.2.1 before we change the CDNS. It seems to be working fine based on the number of posts here in the forum!