Change Account IPv6 in WAP
Assign a shared IPv6, individual address or available subnet allocation to an Eenos account, and understand prerequisites and DNS verification.
Open Hosting → User Accounts → Change Account IPv6 to assign an IPv6 address using the server's configured address inventory. A selected range can allocate an individual address; it is not a request to assign the entire subnet to the account.
Requirements and unavailable state
Use an authenticated administrator WAP session over HTTPS with JavaScript enabled. Demo sessions cannot submit changes. The usable assignment page requires both a main shared IPv6 address and at least one available assignable IPv6 entry.
If these requirements are missing, IPv6 Assignment Unavailable explains the preparation steps:
- Open Basic Setup and configure the server's intended Main Shared IPv6 Address.
- Use Network & DNS → IP Addresses → Add IPv6 Address to prepare an assignable address or subnet.
- Verify provider routing and network readiness, then reopen this menu.
Even if only shared assignment is intended, the current page checks for available inventory before showing the form. Entering a shared address alone does not guarantee the assignment table appears.
Fields and address choices
The table lists User, Domain, Current IPv6 Address, Status and Action, with search and page-length controls. Select Change IPv6 Address for the intended account.
| Dialog field | Meaning |
|---|---|
| Hosting Account | Read-only target username. |
| Domain | Read-only primary domain. |
| Current IPv6 Address | Recorded current account IPv6. |
| New IPv6 Address or Subnet | Required choice from the main shared address and available inventory entries. |
The main shared choice is labeled Main Shared IPv6 with /128. Other choices display an address and its configured prefix length. A /128 represents a single address; other supported ranges allow allocation of an available individual address from the selected range.
The form submits the inventory address behind the selected option and the server normalizes it before allocation. Do not treat this as a free-text CIDR input or assume the displayed range's base address will be the final account address.
Apply and verify
- Confirm account identity and record the old IPv6 address.
- Choose the shared address, individual address or configured range appropriate for the account.
- Select Change IPv6 Address, or cancel/close to stop.
- Review the result message.
- Reload and inspect the actual account IPv6 and allocation, particularly when a range was selected.
- Verify affected domain configuration, local AAAA/DNS data and external IPv6 service connectivity separately.
Verify the allocated address, not only the selected range
The success banner can show the submitted inventory address while the allocation helper returns a different individual address from that range. Confirm the address stored on the account and used by its domains before publishing or relying on external DNS.
The helper normalizes account addresses, sets shared/dedicated status, updates applicable domain IPv6 settings and local DNS, and manages assignment through the allocation workflow. Domains and zones with their own different custom IPv6 are treated separately rather than blindly overwritten. Scoped addresses containing a zone identifier are rejected by the account-DNS update helper.
Choosing the configured shared IPv6 sets dedicated IPv6 status Off; another resulting address sets it On. There is no guarantee of dedicated allocation merely because a range was chosen; verify the outcome and any fallback behavior.
Errors and recovery
| Situation | What to check |
|---|---|
| IPv6 Assignment Unavailable | Configure the main shared IPv6 and assignable inventory, then verify network readiness. |
| Invalid IP / missing selection | Select a supported inventory entry of the correct address family. |
| User not found / User IP v6 change failed | Reload and verify the target and form values. |
| Unable to change user IP v6 / allocation error | Inspect the actual account, domain, DNS and allocation state before retrying. |
| Demo server: this operation is unavailable | Changes are blocked in this session. |
Attempted updates record an account IPv6 audit event using the resulting address. The workflow has multiple writes and no automatic rollback of every subsystem. Failure is not proof that no change occurred.
To return to a previous address, review its current allocation and suitability first. Reapply the intended assignment and verify all affected resources; selecting a broader range again is not a guarantee of receiving the same prior address.
Do’s and don’ts
- Do verify the actual resulting address, routing and public IPv6 connectivity.
- Do coordinate externally hosted AAAA records and allow for DNS caching.
- Do review domains with intentional custom IPv6 assignments.
- Do not assume selecting a subnet assigns every address in it to the customer.
- Do not confuse IPv6 assignment with adding provider routing, registrar DNS or firewall rules.
- Do not rely only on a submitted-address success message to identify the final allocation.
Previous: Change Account IPv4. Next: Change Password.