In short: Reseller customers can use names such as ns1.yourdomain.example and ns2.yourdomain.example. This requires both registrar-level host or glue records and matching DNS records.
| Private nameserver | IPv4 | IPv6 |
|---|---|---|
ns1.yourdomain.example | 77.95.37.24 | 2a02:5300:1:2::2 |
ns2.yourdomain.example | 77.95.37.25 | 2a02:5300:1:2::3 |
Configure private nameservers
- Choose two names beneath a domain you control, normally
ns1andns2. - At that domain's registrar, find Register nameserver, Child nameserver, Host records or equivalent.
- Register each name with the matching IPv4 and IPv6 addresses shown above.
- In the domain's authoritative DNS zone, create matching A and AAAA records for both names.
- Wait for the registry and DNS changes to propagate, then confirm that both names resolve correctly.
- Test with one non-critical domain before publishing the nameservers to customers or adding them to automated welcome emails.
Using them in a billing system
If you use WHMCS, add the private nameserver hostnames to the relevant server configuration only after registration and testing. WHMCS can then include them in hosting-account communications.
If the registrar asks for only IPv4
Registrar and registry capabilities vary. Register the supported values, but keep the matching A and AAAA records in your DNS zone. Contact the registrar if its interface does not explain how to create child nameservers.
Before changing existing nameservers
Do not remove working glue or replace addresses without a migration plan. Keep the old and new configuration available long enough for cached delegation data to expire.
Further reading: InterWorx: Manage DNS records in SiteWorx and WHMCS: Server and nameserver settings.
