Some version of WHM/CPanel come with broken NDC. To fix this:
SSH into your box as root.
(a) Type: cd /scripts
(b) Type: ./updatenow
(c) Type: ./fixndc
(d) Type: service named stop
(e) Type: service named start
1. 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' (write the IP down or remember it for the next step). Then hit 'Add an A Entry for this nameserver'.
Repeat this process for the Secondary Nameserver field.
2. Register Nameservers
Go to your domain registrar and register ns1.yourdomain.com (22.214.171.124) and ns2.yourdomain.com (126.96.36.199) as nameservers. 188.8.131.52 being the primary nameserver IP from step 1 and 184.108.40.206 being the secondary.
These registrations may take a few days to propagate (often as many as 3 days).
3. Reverse DNS
You may need Burstnet to enter a reverse DNS pointer (PTR Record) 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. Send an email to [email protected] with the following...
Please create the following PTR records.
220.127.116.11 - server.mydomain.com (Main Server IP)
18.104.22.168 - ns1.mydomain.com (This of course being your info)
22.214.171.124 - ns2.mydomain.com
4. 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.
5. Initial Nameserver Setup
Go into WHM (Web Host Manager) and select Initial NameServer Setup from the Server Setup menu on the left.
6. Restart BIND
Restart BIND from SSH with (step 5 restarts BIND, but sometimes needs a proper stop and start for it to work):
service named stop
service named start
7. Manual Checks
This process doesn't always work, so there are some things you can check manually via SSH.
Check that the nameservers are correctly specified on NS1, NS2 etc.
Check that there are nameserver entries for each IP. There may also be one for 127.0.0.1 - this is okay.
I'm trying to do step 1 but I get "Sorry, the nameserver ns1.mydomain.com already has the ip 126.96.36.199 assigned to it."
I've tried going to fasthost (where I registered the domain) and delete the current host records but it wouldn't let me. Fasthost support says it's because domains are pointing to the nameservers. Surely companies have moved servers without getting customers to mess around with where there domains are pointing to.