Reseller Name Servers in WAP
Set up to four authoritative nameserver defaults for a reseller's future accounts without rewriting existing account zones.
Open Hosting → Resellers → Reseller Name Servers. The table lists User, Domain, Nameservers, Status and Action. Select Change Nameservers for an active reseller.
Requirements and fields
Use administrator WAP access over HTTPS. Suspended resellers are blocked by the nameserver selection/save validation; demo submissions are blocked. Prepare authoritative nameserver names and any required DNS/glue separately.
| Editor field | Requirement |
|---|---|
| Selected Reseller / Main Domain | Read-only identity. |
| Primary Nameserver (NS1) | Required valid nameserver domain name. |
| Secondary Nameserver (NS2) | Optional valid name. |
| Additional Nameserver (NS3) | Optional valid name. |
| Additional Nameserver (NS4) | Optional valid name. |
Values come from the reseller's saved list. Domain normalization supports DNS-compatible internationalized names. Enter hostnames rather than IPs, URLs or ports. Empty optional slots are removed, so later names can compact into earlier slots on reload.
Save and verify
Review the identity and all four fields, select Save Nameservers, and look for Reseller nameservers updated successfully. Reload and verify the saved list. Attempted updates record reseller audit events.
Future accounts only
This writes the reseller's nameserver defaults used during future provisioning. It does not change existing accounts, domains or DNS zones, create nameserver A/AAAA records, register glue or change domain delegation.
These are authoritative nameserver defaults, not the server's recursive Resolver Configuration. Saving validates names and writes reseller metadata; it does not query DNS to prove readiness.
Errors and recovery
Missing NS1, invalid names, nonexistent resellers and suspended status prevent saving. On unable-to-update errors, reload and inspect the saved state plus server logs. To reverse a successful unintended change, restore the recorded prior names and verify; no automatic history/rollback is provided.
Do’s and don’ts
- Do prepare DNS and registrar requirements before using new defaults.
- Do verify the list and a later authorized provisioning outcome.
- Do not expect existing customers to migrate nameservers automatically.
- Do not confuse syntax validation with working public DNS.
Previous: View Sub Accounts. Next: Reseller Shared IPv4.