Private nameserver for each domain with different Class C ip, possible?

Yes. If you run a reseller or multi-site account with us, you can give every domain its own private nameservers (ns1.yourdomain.xxx and ns2.yourdomain.xxx) resolving to that domain's own dedicated Class C IP. This is the standard setup for operators who want each site to look like an independent host rather than a cluster sharing one nameserver and one address. Below is how it works and how to configure it end to end in WHM.

What a dedicated IP does, and what it does not

Be clear on the value before you build. A dedicated IP with matching private nameservers is a footprint and reputation measure, not a ranking booster. It does not make a page rank higher on its own. What it does is keep each site off a shared address whose neighbours you do not control, and it removes the obvious shared-nameserver fingerprint that ties a group of sites together. That is a defensive benefit for anyone running a network of sites, not a shortcut to better positions. Google evaluates content and links, not the raw fact that a domain sits on its own IP, and stacking sites that clearly exist to manipulate rankings can still fall foul of its spam policies regardless of how the IPs are arranged. Use dedicated IPs to reduce shared-neighbour risk and control your footprint, not as a substitute for genuinely distinct, worthwhile sites.

The package is already set up

You do not need to build the IP routing by hand. In WHM you will find a package we have already created that routes a dedicated IP from your own IP pool to each account as you create it. Create your accounts as normal and each one is assigned an address automatically. If you want every site on a different Class C range rather than simply a different IP, that comes from the range mix on your plan; see multiple Class C IP hosting for how the pools are structured.

Find which IP belongs to which domain

Once the accounts exist, open the List Accounts option in WHM. It shows the IP assigned to each domain. Note which domain is using which IP, because you will type these addresses into the DNS zones in the next step and it is easy to mix them up on a larger network.

Point the nameservers at the dedicated IP

Both ns1.yourdomain.xxx and ns2.yourdomain.xxx should resolve to the same dedicated IP for that domain. To set this in WHM:

1. Click Edit DNS Zone in the left navigation bar and open the zone for the relevant domain.
2. Find the section labelled "Add New Entries Below this Line".
3. In the first box, enter ns1. To the right of that line, select A from the drop-down menu, then enter the IP you noted for this domain in the new text box that appears.
4. In the second box, enter ns2 and do the same, using the same IP.
5. Repeat for the rest of your domains, each pointing to its own noted IP.

Using A records to glue both nameservers to the domain's own address is the ordinary way to run private nameservers, so both hosts answer for the domain on its dedicated IP.

Register the nameservers at your registrar

The last step happens outside WHM. Log in at your domain registrar and update the nameserver records so the domain uses its own private nameservers. Most registrars have a "register a nameserver" or "child nameserver" screen where you enter each host and its IP. The details you register will look like this:

• ns1.yourdomain.xxx >> IP
• ns2.yourdomain.xxx >> IP

Then set the domain to use ns1.yourdomain.xxx and ns2.yourdomain.xxx as its nameservers. The exact screens differ by registrar, so follow their own private-nameserver guidance for the wording and menu names.

Allow time for propagation

After you change nameservers or A records, the update is not instant. Propagation can take up to 72 hours as resolvers around the world pick up the new records. If a site does not resolve to its dedicated IP straight away, wait out the propagation window before assuming something is wrong, then recheck the zone and registrar entries.

For related questions on running several sites cleanly across separate IPs, see the Site Networks and Multi-Site FAQ hub. If you have a case that does not fit the standard package, our team can confirm the right pool and range mix before you start; just get in touch.