Specifying the nameserver’s DNS role in WHM
We need to specify which server is to function as a standalone server — that is, a server that only receives DNS data from the other servers in the cluster.
You do not need to link dedicated nameservers to each other.
Under Dns Role, select Standalone next to each web server’s hostname and IP. This will allow the nameserver to receive information from the web server, but not send data to it.
Setting a nameserver to synchronize data to a web server is not recommended, as it will create extraneous zones on the web server.
In most cases, a DNS-only server should never be set to synchronize to a Web server. The Web server should always be set to synchronize to the DNS ONLY server(s), and the DNS ONLY server(s) should always be set as standalone.
How to Change the Name of RVSiteBuilder in cPanel
If you are using the x3 theme. If that’s not the case, substitute accordingly.
Edit: /usr/local/cpanel/base/frontend/x3/dynamicui/dynamicui_rvsitebuilder.conf
Change the text as follows:
itemorder=>40,version=>1.0,itemdesc=>{Your Text},description=>{Your Text}
Useful SMART Commands
Cpanel script is not very helpful, but you can certainly use these commands for predict and analyze real drive issues:
smartctl -a /dev/hda smartctl -a -d ata /dev/sda <—- for SATA Drives
smartctl -t short /dev/sdb This runs a short test on the drive, you then view the results with the above commands.
Note: you can even just schedule these to run as a cron job and pipe the output to | mail you@youremail.com to automate this.
There are also various scripts you can customize for smartd and smartctl, these scripts are usually in:
There are example scripts included with smartmontools. These are usually located in a location like:
/usr/share/doc/smartmontools-5.33/examplescripts
FTP Connection Issues
On servers running Monolithic kernels (e.g. VPS Virtuozzo/OpenVZ and custom built kernels) ip_conntrack and ip_conntrack_ftp iptables kernel modules may not be available or fully functional. If this happens, FTP passive mode (PASV) won’t work. In such circumstances you will have to open a hole in your firewall and configure the FTP server to use that same hole.
For example, with pure-ftpd you could add the port range 30000:35000 to TCP_IN and add the following line to /etc/pure-ftpd.conf and then restart pure-ftpd:
PassivePortRange 30000 35000
For example, with proftpd you could add the port range 30000:35000 to TCP_IN and add the following line to /etc/proftpd.conf and then restart proftpd:
FTP over SSL/TLS will usually fail when using an SPI firewall. This is because of the way the FTP protocol established a connection between client and server. iptables fails to establish a related connection when using FTP over SSL because the FTP control connection is encrypted and so cannot track the relationship between the connection and the allocation of an ephemeral port.
If you need to use FTP over SSL, you will have to open up a passive port block in both csf and your FTP server configuration.
TCP and UDP Ports for Cpanel Server Firewall
Incoming TCP ports
TCP_IN = “20,21,22,25,53,80,110,143,443,465,587,993,995,2077,2078,2082,2083,2086,2087,2095,2096,2242″
Outgoing TCP ports
TCP_OUT = “20,21,22,25,37,43,53,80,110,113,443,587,873,2087,2089,2703″
Incoming UDP ports
Outgoing UDP ports
UDP_OUT = “20,21,53,113,123,873,6277″
