Set Up Custom Nameservers: Service, Glue and Delegation

Custom nameservers give you names such as ns1.example.com for an authoritative DNS service. Branding does not conceal the underlying provider reliably, grant extra cPanel permissions or create independent redundancy. Separate server configuration, registrar host registration and domain delegation.

1. Prepare an authoritative service

For an authorized cPanel administrator, review WHM > Basic WebHost Manager Setup and the supported nameserver software. Set the intended default nameserver names and correct address records using the installed controls. Do not replace a server’s main IP with a copied VPS address merely to populate a form.

The service must actually host the intended zones and answer authorized UDP/TCP DNS queries. Protect transfers and administration and do not expose an open recursive resolver. Two names or addresses on one machine do not survive that machine’s outage. Plan independent endpoints and the provider’s requirements before public delegation.

2. Register nameserver hosts where required

At the registrar for example.com, create the appropriate child-host/glue registration for ns1.example.com and its real address. Keep the corresponding authoritative A/AAAA data consistent. Ordinary forward records alone do not necessarily create the parent glue needed to break an in-domain lookup dependency.

Use your actual registrar’s host-registration procedure. See GoDaddy host registration or InterServer registration guidance as applicable, not as interchangeable dashboards.

3. Delegate domains deliberately

Preserve website, MX, authentication and verification records at the new authoritative service first. Then change the intended domain’s nameservers at its registrar. Editing NS records only inside a zone is not the same as changing its parent delegation. Coordinate existing DNSSEC DS/key relationships rather than leaving a stale trust chain.

Query the new endpoints directly before cutover and compare parent delegation and recursive answers afterward. Cache lifetimes vary; do not promise worldwide completion in a fixed 24-48 hours. Keep recovery access and the previous service available where appropriate.

Reference: cPanel nameserver setup and scope.

Reviewed October 16, 2026. No custom nameserver, IP assignment, glue, delegation or customer DNS service was configured.