Using custom name servers
A custom name server allows you to run your own name server to respond to DNS requests for your domains. It is also a requirement for VPS and dedicated server customers who wish to have root access on their servers, since with root access you can modify the DNS zones on the server, and having access to our public name server zones would be a security risk.
You can also decide to setup custom name servers for branding purposes, if you would like to hide the fact that your domain's DNS requests are handled by our public name servers. Shared hosting customers can achieve this same branding affect for their domains by instead setting up vanity name servers.
Our public name servers
By default any websites that we host are going to have DNS records added for that website to our public name servers. Currently these are our public name servers:
ns.inmotionhosting.com 126.96.36.199 ns2.inmotionhosting.com 188.8.131.52
Are you using our public name servers?
You can use our domain routing tool to see if your domain is pointed already at our public name servers. Or you can follow the steps below to check your domain's DNS records directly from your computer.
- Open a command prompt window by going to Start and then typing in cmd and hitting Enter.
- Once a command prompt window is up, you'll want to type in the following command and hit Enter
You should now be at the nslookup prompt indicated by a >
Now you'll want to specify that you are just looking to query the (NS) name server records of the domain by typing in the following:
Then hit Enter to be dropped to the next line, and here is where you'll type in your domain name:
For this example we used InMotionHosting.com and we get back our public name servers:
ns.inmotionhosting.com internet address = 184.108.40.206 ns2.inmotionhosting.com internet address = 220.127.116.11
Activating custom 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 instead.
You should have already at this point been given custom name server entries by our system administration team, or you specifically requested for them to be setup. For this example we'll be using the fake domain name MyCustomNameServer.com.
ns1.MyCustomNameServer.com 18.104.22.168 ns2.MyCustomNameServer.com 22.214.171.124
- 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 the IP address you were given for the custom name server.
- Repeat the same step again for the ns2 host as well.
- Now update all of your domains to point to your custom name servers.
After making DNS changes like this, it can take a full 24-48 hours for the settings to fully propagate. Once they have updated, you should be able to query your domain's name server records again, and it should come back with the custom name server settings as the active name server addresses for that domain.
How do I find my custom nameserver IP's
- Log into WHM.
- Go to Home > DNS Functions > Edit DNS zone.
- Select your main domain from the list and click Edit.
You will see your ns1 and ns2 subdomain entries for your custom nameservers. The IP is located there. See image to the right.