Setting Custom DNS/Name Servers on WHM/cPanel

If you are setting up WHM basic configuration, see step 1. If you have already completed WHM basic configuration, and now would like to setup custom nameservers, see step 2.

1. The first time you log into WHM you will have to complete a 6 step basic configuration:

  • Click on I agree/Go to Next Step 2.
  • Enter your email address at Server Contact Email Address (user@domain.com).
  • Make sure your VPS or dedicated server hostname is correctly configured at "Hostname" (configure a fully qualified domain name for the hostname, something like vps.yourdomain.com or server.yourdomain.com).
  • Click on Save & Go to Step 3 and after click on Go to Step 4.
  • Enter the custom nameservers at "Nameserver 1" and "Nameserver 2" (ex. ns1.yourdomain.com and ns2.yourdomain.com).
  • Check the box with Add "A Entries" for all Nameservers
  • Enter your VPS or dedicated server main IP at ns1 and the second IP at ns2. You can see your allocated IPs in your Client Portal.
  • Check the box with Add "A Entries" for Hostname.
  • Click on Save & Go to Step 5 and after this click on Save & Go to Step 6.
  • Click on Finish Setup Wizard.
  • Go to "Tweak Settings" and ensure "Enable WHOIS lookups for the nameserver IP manager" is set to "Off" (if this is setting is set to "On", assigning an ip to a nameserver can take a long time).
  • Go to "Basic cPanel & WHM Setup" -> "Basic Config" and enter your main IP of your VPS or dedicated server to "Shared Virtual Host IP" (first field).
  • Go at the bottom of this page and make sure you have the correct nameservers entered at "Nameserver 1" and "Nameserver 2" then push the "Assign Ip Address" button for both the nameservers.
  • Don't forget to add this namerservers at your register, from where you bought your domain.

You are done with the nameserver configuration, don't forget to update cpanel before adding production accounts on the vps or dedicated server.

You can use the "Upgrade to Latest Version" button from WHM to make sure cPanel is up to date.

2. If you already did the 6 steps basic configuration but you didn't set up custom nameservers, please follow the next steps:

  • Go to "Tweak Settings" and check if "Enable WHOIS lookups for the nameserver IP manager" is off (if you don't do this, assigning an ip to a nameserver can take a long time).
  • Make sure your VPS or dedicated server hostname is correctly configured at 'Change Hostname' -> 'Current Hostname' (something like vps.yourdomain.com or server.yourdomain.com)
  • Go to "Basic cPanel & WHM Setup" -> "Basic Config" and enter the main IP of your VPS or dedicated server into first field.
  • Go at the bottom of this page and make sure you have the correct nameservers entered at "Nameserver 1" and "Nameserver 2" then push the "Assign Ip Address" button for both the nameservers.
  • Push the "Add an A entry for this nameserver" button for both the nameservers and Add Entry.
  • Click Save Changes at the bottom of the page.
  • Don't forget to add this namerservers at your registrar, from where you bought your domain.

You are done with the nameserver configuration, don't forget to update cpanel before adding production accounts on the vps or dedicated server.

You can use the "Upgrade to Latest Version" button from WHM to make sure cPanel is up to date.

Was this answer helpful?

 Print this Article

Also Read

Recursively Delete Directory Using SSH

This article will demonstrate the process of Recursively deleting an entire directory using SSH...

Reboot Linux Server Using SSH

This article provides a guide for Rebooting a Linux-based VPS or Dedicated Server Using the SSH...

Reloading a Dedicated Server Operating System

This article will provide instructions for reloading your Dedicated Server operating system at...

Locating php.ini file

A critical file you often need to manage is the php.ini file. It controls many import aspects of...

Resolve "Configure: Error: No Acceptable C Compiler Found in $PATH"

When installing software to your Ubuntu VPS or Dedicated Server, you may encounter an error:...