A passion for web development



Configuring cpanel whm

The remote web administration for web servers called cpanel is absolutely the best because it is easy to use and setup. It requires no hardcore IT skills, nevertheless, the power of cpanel won't be appreciated if IT and server administration are not well comprehended.

What makes working with servers to be a complex subject is the dns, mail, httpd, etc setups and configuration. Everything needs planing and server setup requires careful planning in order to achieve successful configurations. The following areas should be understood.

Cpanel has a section called whm.
Cpanel is the virtual host server configuration while whm is machine GUI for root or user with privileged access rights such as re-sellers.
End users only have access to virtual host

cpanel login ports: http://ipaddressOrDomain:2082 or https://ipaddressOrDomain:2083.
whm login: https://ipaddressOrDomain:2086 or https://ipaddressOrDomain:2087

Note the above has two urls set each and two ports each. The first one is using http while the other url is using secure http secure.

If you are using a domain, make sure the domain is pointing to your server ipaddress. To achieve this, you have to create a glue or a host. Example Godaddy allows you to register a domain host name to be pointing at a given IP.

Registering a domain name server for cpanel.

By default cpanel comes with the providers own network servers configured by the data centre where the server is leased, in order to use your own dns, you have to register the domain name servers. This is what can confuse lots of people. Registering the domain name sever requires no more than creating hosts or glues mentioned above and that the host should directly point at your dns which often is the same as the cpanel root or machine IP.

Often creating hosts as follows:

The first two hosts can share the same IP but ns1 and ns2 should not share even though it can work.

If you haven't got a second IP like most cases in vps comes only with one free IP and even if you have two free IPs on a dedicated server using two IPs dns1 and dns2 on the same machine doesn't really provide the solution of slave / master but this is another story I won't be talking about right now.

Now you know your IPs and your domains and how they are linked. Now to proceed to cpanel setup You can approach this in many ways but I will be mentioning what I found to be the best approach; Leave the default setups for the root user in relation to the whm and dns in other word carry on using the dns servers provided by your server services provider. However now you can give each newly created user the new servers created above ns1.domainname.com and ns2.domainname.com. Also you can change the host name of the server to the new servername.domainname.com if you wish but it is optional as the server was already given a host name from the initial set up by the data center.

When you apply for a private virtual server or and a dedicated with cpanel, the service provider will give you the details of logging in as well as initial master control over the services such as restart, reset etc. for example heart internet enables the user to use a reference as a glue but this will override the fact that the dns servers have to be registered with the domain provider if you are willing to assign it to your users and be recognized. In other words you choose either to register a domain name server or use reference but both work as a glue in the end of the day,

Now we have registered our domain servers and we have configured the new users to use the new dns. In an event there is only One IP address then use only one ns1 and use the default ns2 for the system. The default name servers will not resolve to the IP for addon domains or parked domains, and it is useless beyond the whm. Resolver configuration won't be needed in most cases and it is already configured if you have purchase a service. To resolve the domains then it is best to use the domain server reference and IP configuration provided by the server provider account.

Don't get confused, server provider account is the one used to purchase the services and not in the cpanel or whm. In that area you can use the basic dns configuration mentioned above to set up and point a domain such as creating dns1.yourdomain.com

To recap the above as follows:

1- Get the logging details from the where you purchased the server with cpanel
2- Cpanel is separate from the server and it is installed after purchasing the server or configuring your own machine at home
3- Your data-center will install cpanel with whm or you can take this task by contacting cpanel and purchasing directly from the cpanel company.
4- Once cpanel is installed, a url with ports is used to access the cpanel
5- Before pointing any domains, your default host name is given to you as subdomain from the company you bought the service from.
6- Cpanel comes with default domain name servers but sometime you just cannot be without assigning a registered name server of your choice that can be resolved to the correct IP. You will need your own dns in cases when you have lots of domains configured to a certain dns so that you need to reconfigure the same dns in the new server other wise you will have to go to the domain provider dns configuration to point each domain to the new server. Imagine if you have 50,000 domains!
7- You can register a domain name server from the domain name provider and you only need one domain with two dns sub domains.
8- Use these domains in the whm for user dns setup that can be found under (Edit reseller privileges & nameservers) from (Resellers) in whm accessed by root

That's all what it takes to setup cpanel accounts.

I hope you are ready to configure cpanel, good luck.

Send me an email if you need help

01902 637 708