Using Custom Nameservers as a Reseller
In this tutorial we will guide you through the process of using your own nameservers. First you must create the ‘A records’ for the nameservers, activate the nameservers, then assigning them in the Web Host Manager (WHM). Then going forward, when you create a new cPanel, it will use the default nameservers.
This will not change the nameservers for existing cPanel accounts. They will have to Update their nameservers to the new ones, with their registrar.
Creating Nameservers (as an ‘A record’)
- Login to the cPanel for the domain you want included in the Nameservers. For example if you want to create: ns1.example.com, you would login to the cPanel for example.com
- On the left side of cPanel under stats, locate and copy your Shared IP Address. You may have to click the expand stats link.
- Under Domains click the Advanced DNS Zone Editor button.
- In the Add a Record section, fill in the fields as needed for each nameserver you want to create. Below is a brief example of what to enter in the fields.
Field Name Example Name Enter the nameserver you want to setup here, for example: ns1.yourdomain.com TTL You can enter any positive number here, but I recommend entering 14400, which is quite standard across the industry. Type Select A Address Enter the Shared IP you viewed earlier in cPanel (in step 1).
After filling in the fields, click the Add Record button.
You will see a message stating “Added record”
Activating your name servers
If your server has been setup with custom name servers, but your domains are still pointed at our public name servers you'll want to update these so that they are using your custom name servers.
You should have already created the nameservers at this point, for this example we'll be using the fake domain name MyCustomNameServer.com:
ns1.MyCustomNameServer.com 188.8.131.52 ns2.MyCustomNameServer.com 184.108.40.206
- Login to your domain Registrar where you registered the MyCustomNameServer.com domain name.
- Most Registrars will have a section similar to Maintain name servers under this domain, or it's sometime referred to as glue, or host records as well.
- Typically you'll just need to enter in the part before your domain name ns1 for instance, and then your shared IP address.
- Repeat the same step again for the ns2 host as well.
Activate Your New Nameservers in AMP
If your domain is register through us, you can activate (also knows as glue) your Custom Nameservers in AMP.
- Login to AMP.
- Move your mouse over the DOMAINS menu, and click the MANAGE DOMAINS link.
- Click the domain name you want to edit from the list.
- On the next screen click Create custom nameservers.
- In the Add Name Server section enter your custom nameservers, and your Shared IP for both nameservers. Click the Submit button to save your changes:
You will then see your new nameservers listed.
Assigning Nameservers in WHM
- Login to WHM.
- In the left navigation menu, click Server Configuration, then click the Basic cPanel & WHM Setup.
- You will then see the current nameserver assignments.
Enter your new nameservers, and click the Save Changes button. You will then see a message stating “Your account’s nameservers have been set to ns1.example.com and ns2.example.com.This system has no free IPs.”
Remember, any DNS modification such as a Nameserver change can take up to 24 hours to propagate.Congratulations, now you know how to use custom nameserver as a reseller!
We value your feedback!
There is a step or detail missing from the instructions.
The information is incorrect or out-of-date.
It does not resolve the question/problem I have.
new! - Enter your name and email address above and we will post your feedback in the comments on this page!
2013-11-18 12:49 pm
I've followed all the steps.
But when I try to change the Primary and Secondary field (with my newly created nameserver) in the Delegation Details here :
it says that:
"ERROR: This is not a valid entry, please resubmit."
2013-11-18 2:40 pm
It sounds like the system is either not seeing your newly created entries, or that they were not created correctly.
I see a note on your account from just a bit ago stating we had to clear out old DNS entries for you. Are you still having any issues at all?
2014-02-27 5:10 am
After I did all this changes, and waited for a week. when I do dns Look up on the domain I still get your NS server (ns1.servconfig.com,ns2.servconfig.com) . and our NS shows also. altough in my register has nothing enterd about your NS only ours...
2014-02-27 8:51 am
If you have created your custom nameservers, you will still need to re-point your domains to them. If you have already pointed your domain to the custom nameservers at your registrar, but a whois lookup is still showing old information, you would need to contact your registrar as something may have not updated correctly.
2014-03-06 4:37 pm
According to this instructions both of the record point to the same IP address so there is no redundancy if using the custom name server option which is not good. Is there any way to have custom name servers with Inmotion and maintain redundancy?
2014-03-06 5:42 pm
If you would like to have name server redundancy, you could follow the steps in our vanity name servers guide to set this up.
You would just need to make some DNS entries for our reseller public name server IPs:
So if the vanity domain you wanted to use for your name servers was example.com, you'd just setup your ns1/2 records pointing to those IPs:
Then you'd want to follow the other steps in this article about activating your name servers at your domain Registrar, and then assigning those name servers in WHM for your reseller account.
If you had any other questions at all, please let us know!
2014-10-01 5:47 pm
Can I used vanity NS and Custom NS at the same time, in order to get good enough redundancy?
2014-10-01 5:56 pm
Thanks for the question! We actually have an article on the Vanity name server. It's not really necessary to have both and it does not give you any advantage to use both. So our suggestion is to use one or the other. Please read through our documentation for more details on either name server type.