We’ll show you the ropes in how to setup cpanel nameservers and configure them properly so you can run ns1 and ns2.yoursite.com
This guide will show you the ropes in how to setup cpanel nameservers and configure them properly so you can run ns1 and ns2.yoursite.com. Once your nameservers are setup clients can then use your own private nameservers for their domains.
1. Regiser your domain
Register the domain name you would like to use.This domain will be used as your nameservers – eg ns1.yourdomain.com and ns2.yourdomain.com
2. Additional IPs
Have 2 available IP addresses for your server that aren’t in use.You will need to contact you provider to obtain these IP addreses.
3. Registering the Nameservers
Now login to your domain management page for the domain you registered and register ns1.newdomain.com and ns2.newdomain.com as nameservers (registries normally have a special facility for doing that). The registry may also have a facility to propogate these nameservers around the foreign registries – if so, you should use this facility.
These registrations may take a few days to propagate (often as many as 3 days).
4. Reverse DNS
You may also need to get your data centre to enter a reverse DNS pointer for your nameservers. You’ll need to let them know each nameserver and its IP address. Sometimes you can suffer non-delivery of mail if you don’t so this. Reverse DNS pointers can take a while to propagate.
Setup a reverse on the IP address for your domain
5. Broken NDC/BIND
My version of WHM/CPanel came with a broken NDC. To fix this:
SSH into your box as root.
(a) Type: cd /scripts (b) Type: ./updatenow (c) Type: ./fixndc
Go back into WHM, go to the Restart Services section in the left menu and click DNS/Nameserver (BIND).
You will need to do this if you start getting ‘ndc’ errors when you are doing anything DNS related in WHM.
6. Setup Nameservers In WHM
Go into WHM (Web Host Manager) and select Edit Setup from the Server Setup menu on the left. Enter ns1.newdomain.com in the Primary Nameserver field. Hit ‘Assign IP Address’, then hit ‘Add an A Entry for this nameserver’.
Repeat this process for the Secondary Nameserver field.
7. Tidy Up Junk Nameservers
Go into WHM (Web Host Manager) and select Manage Nameserver IPs from the Server Setup menu on the left. Remove any nameservers you don’t recognise. This is just a tidy up exercise in case anyone’s set anything up on the box before you.
8. Initial Nameserver Setup
Go into WHM (Web Host Manager) and select Initial NameServer Setup from the Server Setup menu on the left. Run this.
9. Restart BIND
Restart BIND (step 7 restarts BIND, but we’ve known it to need a proper stop and start for it to work) from SSH with:
service named stop service named start
10. Manual Checks
I don’t know what it is about this process, but it doesn’t always work, so there are some things you can check manually via SSH.
Check that the nameservers are correctly specified on NS, NS2 etc.
EG: scroll to the name servers section…..
NS ns1.yournameserver.com NS2 ns2.yournameserver.com
Check that there are nameserver entries for each IP. There may also be one for 127.0.0.1 – this is okay. I’m led to believe (by the ‘man’ entry for resolv.conf) that this isn’t a particularly important file, but I changed mine to read:
domain mybox.com search mybox.com nameserver 127.0.0.1 nameserver 220.127.116.11 nameserver 18.104.22.168
Where ‘mybox.com’ is the main domain of my server, and ‘22.214.171.124’ and ‘126.96.36.199’ are the IP addresses of my primary and secondary nameservers.
resolv.conf is used to lookup names that are not in FQDN format.
Check that there are entries for each IP acting as a nameserver.
Original topic: (link)