how to use access hash in linux dedicated server?
Remote Access Key or access hash in WHM is a cPanel feature that allows external servers and software to communicate with a cPanel & WHM server. It is also known as an access hash. You can use this access key for automatic account creation scripts, external billing software, and to allow servers in your DNS or configuration clusters to exchange records. Silicon House provides the fully managed dedicated server with the full root access with the unlimited WHM/cpanel license. Remote Access Key is possible in the dedicated platform.
Generate a new access key
To generate a new access key, perform the following steps:
1.Click Generate New Key.
2.Copy and paste the new access key to the appropriate file or location on the remote server(s) that need to communicate with your web server.
3.To configure a DNS server cluster.
A DNS cluster is a group of nameservers that share records, which allows you to physically separate nameservers that handle the DNS requests from your web servers. This interface allows you to configure a DNS cluster and add servers to an existing DNS cluster.
To configure your DNS cluster, you must meet the following minimum requirements:
1.Clusters must include at least two servers.
2.You must have at least one web server with cPanel & WHM installed. A DNS cluster that includes multiple cPanel DNSONLY servers and cPanel & WHM servers is also acceptable.
3.All machines in the DNS cluster must have cPanel & WHM or cPanel DNSONLY version 11 or higher installed. Some features may not work with older versions of cPanel & WHM.
4.All machines configured with PowerDNS must have DNSSEC disabled.
4.The Configuration Cluster interface allows you to link a master server to one or more additional servers in the configuration cluster. You can then choose to copy server configuration settings from WHM’s Update Preferences interface
The Configuration Cluster interface displays a list of all of the servers that you linked to the currently-authenticated server.
1.The server’s IP address, or the name that you assigned to the server
2.The username of the server’s root-level account. This value defaults to the root user.
3.The signature version of the server’s remote access key or API token.