Create private nameservers and the matching DNS records

Ask your hosting or DNS provider for the approved nameserver hostnames and IPv4 or IPv6 addresses for your service. A reseller hosting plan can have different DNS permissions from a server you administer directly. Use assigned infrastructure, not an arbitrary website IP.

1. Sign in to the registrar account for the parent domain, such as example.com.
2. For a domain registered with us, open Domains > My Domains, select the domain and use Private Nameservers when available.
3. Register each nameserver hostname with its actual assigned address. If the form requests only the prefix, enter ns1 rather than repeating the whole domain.
4. Repeat for every required nameserver and confirm the registrar accepted the host objects.

If the parent domain is registered elsewhere, create the hosts at that registrar. An ordinary A record in a different DNS account cannot replace the registrar's glue workflow.

In the authoritative zone for the parent domain, add the required A and, where supported and operational, AAAA records for the nameserver hostnames. The values should match the real servers and any glue records.

In Nabtech DNS Manager, use the normal record editor. If the parent zone is managed in cPanel or another provider, edit it there instead. Check which nameservers are authoritative before choosing an editor.

Query each new nameserver directly for a test zone and confirm authoritative answers. Then assign the nameservers to the relevant domains through their registrar delegation controls. Check both public delegation and record consistency.

Do not add AAAA glue or records unless the DNS service is reachable over IPv6. Two different names pointing to one unavailable server do not provide meaningful resilience.

Suppose an authorised DNS service assigns 192.0.2.53 and 192.0.2.54 to your two branded nameservers. These are documentation addresses, so replace them with the real assigned values. The following shows the matching forward-zone records in BIND notation.

ns1.example.com.  3600  IN  A  192.0.2.53
ns2.example.com.  3600  IN  A  192.0.2.54

Read the result: The records make the nameserver hostnames resolve inside your zone. Registering the same hostnames and addresses as child nameservers or glue at the registrar is a separate step. Delegating example.com to those nameservers is another separate operation, and the DNS service must already answer for the zone.

Verify every server directly before changing delegation. Two names pointing to addresses that do not run your DNS service provide no redundancy. Keep the registrar host objects and forward A or AAAA records consistent when an address later changes.

For a future nameserver IP change, update the registrar host object and authoritative A/AAAA records through a coordinated plan. Keep old service reachable while cached glue expires. Do not delete a host still used by customer domains; move those delegations first.

Bring the new address online with the required customer zones before changing public references. Query each affected nameserver directly at its new address and retain a rollback path until both glue and ordinary address caches have moved.

• Change nameservers for a domain registered with us
• Add, edit and remove DNS records in the client area
• Synchronize a DNS package across multiple servers and select its master
• Check DNS propagation and find the source of an old answer

• Dynadot: Register private name servers

• ISC BIND: dig and delv reference