Skip to main content

Using ELevate on a DNSOnly server in a DNS cluster

Comments

13 comments

  • cPRex Jurassic Moderator

    Hey there!  It might be best to remove it just so the rest of the cluster members don't see it as being offline, but I can't think of a reason you'd *have* to remove it.

    0
  • PWHosting-Admin

    Thanks cPRex!

    1
  • ffeingol

    I'd be interested in hearing how your ELevate goes.  We're planning on doing the same thing with our DNS cluster over several weekends.

    1
  • PWHosting-Admin

    ffeingol, We don't have anything scheduled yet, but I would expect it to happen in the next couple of weeks. I'll try to remember to circle back and update this post with how it went.

    1
  • grame jess

    Yes, it's recommended to remove the server from the DNS clustering before upgrading it to AlmaLinux 8. This ensures that there are no conflicts or issues during the upgrade process. Once the upgrade is completed successfully, you can then add the server back to the DNS clustering. 

    0
  • PWHosting-Admin

    ffeingol I'm not sure if you've already tried this, but it worked perfectly for us when I ran the scripts. I cleaned up any blockers that the script reported and removed the server from the cluster. When I was done I added it back to the cluster and everything was as it was before, just running on AlmaLinux 8. Hopefully your experience is the same.

    0
  • clopezi

    I've recently done this exact process and everything it's working fine. I've done this on a OVH VPS (I didn't expected to work fine on a VPS, so it's a very welcomed surprise).

    I didn't disconnect from the Cluster before.

    1
  • cPRex Jurassic Moderator

    clopezi - thanks for the feedback!

    0
  • Rocha Neto

    After correcting the brokers, I upgraded and I have problems in part 4.

    The system was updated to almalinux but in the middle of the process the system lost network connection and the process was interrupted.

    I did this in a clone of a cpanel dns, and at the moment I am unable to resolve names. It's a VPS, I lost SSH access. But I still have the console. Via the console I can ping ips, but names do not ping at all. I spent a few hours trying to fix it, without success.

    Any suggestion?

    NetworkManager seems to not want to receive a valid dns. /etc/resolv.conf is not recognized.

    Thanks.

    0
  • clopezi

    It's a DNS only server, recycle it from scratch. You will take 5 minutes to configure it again, don't lost your time hehe.

    1
  • Rocha Neto

    Thanks for your answer, if it was just DNS I would have done that. I used DNs just as an example, lol. ahahahaha. I have other cPanel to do, and I wanted to see how Elevate would work. First test and it didn't work.

    I'm considering making the cpanel servers from scratch too, and migrating the accounts. Unfortunately, despite the good work that has been done on Elevate, it leaves questions, and I can't risk it.

    0
  • clopezi

    Ah hehe. I'm done also many servers from scratch and restore backups, elevate it's a risky operation and even more when you don't control the boot system

    0
  • Vincenzo Conn

    When upgrading your DNSOnly servers from CentOS 7 to AlmaLinux 8, it's a good idea to temporarily remove the server from the DNS cluster before proceeding with the upgrade. This ensures that any potential issues during the upgrade won't affect your cluster's stability. Once the upgrade is successfully completed, you can re-add the server to the cluster. By doing so, you maintain the integrity of your DNS services throughout the transition and avoid any disruptions that could arise from an unexpected error during the upgrade process.

    0

Please sign in to leave a comment.