Skip to Content
Browse documentation

Reseller Shared IPv6 in WAP

Set a reseller's shared IPv6 address or range-derived allocation for future accounts and verify the resulting stored default.

Open Hosting → Resellers → Reseller Shared IPv6 to change the IPv6 default for future provisioning.

Availability and requirements

Use administrator WAP access over HTTPS with JavaScript enabled. Both a main shared IPv6 in Basic Setup and available assignable IPv6 inventory are required to show the usable page. Otherwise the unavailable page directs you to prepare shared configuration and add an IPv6 address/range. Suspended resellers and demo submissions are blocked.

Confirm address/range routing and record the prior reseller default before changing it.

Table and dialog fields

The table lists User, Domain, Shared IPv6, Status and Action. Select Change Reseller Shared IPv6.

FieldMeaning
Reseller AccountRead-only target.
Current IPv6Existing saved default.
New Shared IPv6 AllocationRequired choice of shared IPv6, individual address or configured range.

A /128 entry identifies an individual address. A broader allocation can return an available individual address from that range, rather than the displayed base address. The view normalizes IPv6 input before calling allocation; this is a selector, not a free-text CIDR editor.

Apply and verify

Select the intended allocation and confirm Change Shared IPv6, or cancel. Reload after the response and verify the actual stored address, not just the selected range shown in the success message. Review allocation/routing separately.

Future accounts only

The helper changes the reseller's shared IPv6 metadata and releases the previous recorded allocation through its helper. It does not migrate existing subaccounts, domains or DNS zones.

The audit event records both the submitted selection and resulting address. For existing account migration use Change Account IPv6.

Errors and recovery

Unavailable inventory, invalid IPv6, missing reseller or suspended status require addressing the prerequisite first. On allocation or write failure, inspect actual metadata and usage state before retrying; multiple effects are not automatically rolled back. Reselecting a broader range is not a guarantee of recovering the same previous address.

Do’s and don’ts

  • Do verify the final stored address and its provider routing.
  • Do preserve external DNS and existing-account dependencies separately.
  • Do not assume selecting a subnet assigns the whole range to every customer.
  • Do not treat a success message as an IPv6 connectivity test.

Previous: Reseller Shared IPv4. Next: Suspend or Unsuspend.