Do I get private nameservers for each domain

Yes, on every plan and at no extra cost. Each domain can run its own ns1 and ns2 pair pointed at addresses from your own allocation, created from the control panel. Your domains do not have to share a nameserver pair, which matters because a shared pair is the second-most-visible thing a group of sites can have in common after a shared address.

What a private nameserver is

When someone looks up your domain, the answer arrives from a nameserver, and which nameserver answered is public information. On default hosting that answer names the provider's shared pair, and the same pair answers for every other customer on the platform.

A private nameserver replaces that with names under your own domain, answering from your own address. The lookup returns something belonging to you rather than something belonging to a hosting company, and two of your domains using two different private pairs return two unrelated answers.

Why per-domain rather than one pair for the estate

This is the part people get wrong, and it is worth being direct about it. Setting up one private pair and using it across forty domains feels like progress and achieves very little. The answer is no longer the provider's, but it is still one answer shared by forty domains, and grouping them is still a single query.

A pair per domain is what removes the shared answer. Since it costs nothing here, the only reason not to do it is not knowing it matters.

What it does and does not buy

It removes one grouping attribute. It is not a ranking factor and nobody should tell you it is. Combined with address diversity, it means the two cheapest checks anyone can run on your estate both come back empty.

What remains untouched is everything else: registrar batches, identical templates, a shared analytics identifier, a mechanical link graph. Nameservers are one axis of the same job that address diversity does, and neither substitutes for the non-technical work.

Practical notes

• Point each pair at a different address. Private names on one shared address rebuild the pattern in a different place.
• Glue records live at the registrar. The panel creates the nameserver; the registrar has to be told the address, or nothing resolves.
• Certificates follow DNS. Free SSL is issued automatically once the domain resolves, so get the delegation right first.

The step-by-step setup is in Nameservers and DNS, and the reasoning about footprints is in IP Diversity.