-
cPanel
-
- Mailing Lists
- Default Address
- Autoresponders
- Forwarders
- Email Accounts
- Spam Filters
- Track Delivery
- Global Email Filters
- Email Filters
- Address Importer
- Encryption
- Email Disk Usage
- Calendar Delegation
- BoxTrapper
- Configure Greylisting
- Email Routing
- Filter Incoming Emails by Domain
- Email Deliverability
- Authentication (SPF and DKIM)
- Show Remaining Articles ( 4 ) Collapse Articles
-
-
WHM
-
- SSH Password Authorization Tweak
- Apache mod_userdir Tweak
- SMTP Restrictions
- Compiler Access
- Configure Security Policies
- Password Strength Configuration
- cPHulk Brute Force Protection
- Security Questions
- Manage External Authentications
- Two-Factor Authentication
- ModSecurity™ Vendors
- ModSecurity Configuration
- Manage root’s SSH Keys
- Manage Wheel Group Users
- Host Access Control
-
- Terminate Accounts
- Quota Modification
- Modify an Account
- Change Site’s IP Address
- Create a New Account
- Manage Account Suspension
- Upgrade/Downgrade an Account
- Limit Bandwidth Usage
- Force Password Change
- Email All Users
- Reset Account Bandwidth Limit
- Password Modification
- Skeleton Directory
- Rearrange an Account
- Raw Apache Log Download
- Modify/Upgrade Multiple Accounts
- Web Template Editor
- Unsuspend Bandwidth Exceeders
- Show Remaining Articles ( 3 ) Collapse Articles
-
- Articles coming soon
-
- Articles coming soon
DNS Cluster
Log in to your whm>> Server Configuration>>DNS Cluster
1) Let’s start setting up a cluster. Scroll down a bit to Cluster/Remote Access.
2) Click the Configure Cluster link.
3) First, you must enable the cluster by clicking this radio button.
4) Then, click Change.
5) Return to the Cluster Status page.
6) Now, it’s time to add a server to the cluster. Scroll down.
7) Enter the server’s IP address.
8) Configure the server with this button.
There isn’t much here to configure. You’ll generally want to leave the login name as root.
You need the server’s Remote Access Key. You’ll find out more about these in a later series; just know this is what the two servers will use to communicate rather than using their respective root passwords.
9) Click this link to go directly to the correct page in that server’s WHM.
10) Click here, then press CTRL+A to select the entire access key.
11) Return to the previous page.
12) Click here, then press CTRL+V to paste the key.
13) Click Submit.
Success! The two servers have had a Trust Relationship established between them. It has also been established in reverse automatically, so we don’t need to go there and repeat the process.
14) Return to Configure Cluster.
15) Change the DNS Role of the nameserver we just added to Synchronize Changes.
16) Then, click Save.
Our main server is now set up to Synchronize all DNS changes to the nameserver. Note that enabling this does not enable the reverse — synchronization from the nameserver to the main server is still off.
17) Add any remaining servers to the cluster in exactly the same fashion.
The relationship between the main servers in your cluster should always be set to Standalone, while main servers should should be set to Synchronize Changes to all nameservers.