cPanel multi server aka cPanel cluster – How it helps your webhosting business
Many see cPanel multi server (aka cPanel cluster) as a way to prevent business downtime. The logic goes that even if one server fails, the other servers can keep websites and mail online. But, how true is that?
In our role as Hosting support specialists for web hosting companies, Bobcares engineers manage hundreds of cPanel servers. We setup and manage several cPanel cluster infrastructure as a part of this cPanel server management services.
From this experience, we could see that though cPanel clusters cannot totally prevent a business downtime, they be used to minimize the impact of a downtime, and to simplify server administration.
cPanel multi-server cluster – Do you need it?
As of version 11.56, cPanel offers DNS Cluster for DNS high availability and Configuration Cluster for easier server management. If you already have cPanel servers, here’s how cPanel clusters can help you:
1. DNS cluster – How we configure them to prevent service downtime
cPanel creates 2 name servers for each website created in a server (say, ns1.website.com and ns2.website.com). By default, both these two name servers are created in the same physical machine.
This poses a couple of issues:
- In the event of a server crash, DNS will stop working. This brings down both website and mail – even if the mail is hosted elsewhere (like Google Apps).
- If a website needs to be moved to another server due to resource constraints or other reasons, the name servers need to be changed, leading to extensive downtime.
A single website downtime can affect your customer’s business. We help web hosts deliver quick resolution to these issues using our 24/7 US based phone support. Learn More.
To prevent such downtime, we setup central DNS clusters for our customers. The DNS of all websites would be hosted in 2 or more dedicated DNS servers.
This way every website will have the same set of name servers (eg., ns1.webhostingcompany.com, ns2.webhostingcompany.com), and even if one server fails, other servers will ensure that the services are up.
With these DNS clusters, we’ve been able to:
- Prevent mail bounces using a secondary MX entry for domains, that routes mails to a backup mail server.
- Avoid web or mail downtime during website migrations to other servers. Since name servers are the same for all domains, there’s no need for complex DNS changes and prevents associated downtime.
- Reduce customer complaints and support tickets that happen during domain migrations.
Many of the name server clusters we’ve implemented were based on open source BIND servers. cPanel has a similar solution called DNSONLY. With this, cPanel servers can be setup to store DNS records in a remote DNSONLY cluster.
When we setup DNSONLY clusters, we maximize the cluster effectiveness and security by:
- Setting up the name servers in separate geographical locations – This ensures that a network issue won’t bring down both servers.
- Making all name servers “masters” – This helps to lower DNS update delays. When a DNS record changes, all name servers in the cluster are updated at the same time. This avoids propagation delay among name servers.
- Securing the cluster against cache poisoning, and other attacks – An attack on the cluster can bring down all websites. We prevent it through a series of DNS security tweaks.