Skip to Content
Browse documentation

Change Hostname in WAP

Change the Eenos server hostname through WAP, understand FQDN validation and plan DNS, reverse DNS and certificate checks.

Select Eenos → Preferences → Change Hostname. The page heading is Change Host Name. Use it to change the operating-system hostname that identifies this server.

Requirements and preparation

  • Sign in to WAP with administrator access over HTTPS.
  • Choose a fully qualified domain name (FQDN) under a domain you control, such as server.example.com.
  • Plan the hostname's forward DNS records and the main IP address's reverse DNS (PTR) record. The page explicitly reminds you to point the PTR record to the server hostname.
  • Check services, panel access URLs and certificates that depend on the current name. Retain the previous hostname and an independent way to access the server.
  • The server must have /usr/bin/hostnamectl available for the operation.

Demo sessions cannot apply a hostname change.

DNS and certificates require separate attention

This action changes the system hostname. It does not create DNS records, change provider-managed PTR records, issue certificates or rewrite every service configuration that uses the old name. Prepare and verify those dependencies separately.

Fields and controls

Field or controlPurpose
Current Host NameRead-only hostname obtained from the server. The linked name opens https:// followed by that hostname in a new tab, without adding the WAP port.
Enter New Host NameRequired text field for the intended FQDN. The placeholder is an example, not a saved value.
Change HostnameValidates and submits the hostname change.

The new-name input starts empty; it is not prefilled from the current hostname.

Hostname validation

Use a name such as server.example.com, without https://, a path or a port. Avoid spaces and underscores. Each label must start and end with a letter or digit; hyphens are allowed inside a label. Each label can contain at most 63 characters, and the hostname can contain at most 253 characters.

The server requires at least two dot-separated labels. The browser additionally expects a final alphabetic label of 2–63 characters. Use an ordinary FQDN without a trailing dot so both validation layers agree. This form does not automatically convert Unicode hostname input; use a valid ASCII DNS representation when needed.

Surrounding whitespace is stripped by the form. The change handler lowercases the hostname before applying it. Format validation does not check domain ownership, DNS resolution, PTR alignment or certificate coverage.

Change the hostname

  1. Review Current Host Name and confirm that this is the intended server.
  2. Record the current name for recovery and review the DNS and certificate dependencies.
  3. Enter the intended FQDN in Enter New Host Name.
  4. Select Change Hostname.
  5. Look for Host Name changed successfully.
  6. Reload the page and verify Current Host Name. You can also review the identity shown in the Dashboard after refreshing it.
  7. Verify the new name's forward DNS, PTR, certificate coverage and affected service configuration separately before relying on it for access.

The handler calls the operating system's hostname-management tool and records the result as a configuration audit event. It does not explicitly restart the hosting services or reboot the server.

The hostname link is not the WAP login shortcut

The Current Host Name link opens HTTPS on the default port. For the secure WAP login address, include port 5555 as described in First Login. Only use a hostname for panel access after checking its DNS and certificate configuration.

Errors and recovery

Message or situationWhat to do
Required-field or empty-hostname errorEnter a nonempty FQDN.
Please enter a fully qualified hostname, such as server.example.comUse a dot-separated server name rather than a single-label name.
Please enter a valid hostname / server hostnameCheck label lengths, allowed characters, dots and the final domain label.
Demo server, this operation is unavailableThe session cannot apply this change.
Unable to find /usr/bin/hostnamectl. Command missingHave the administrator investigate the missing operating-system tool; the page does not install it.
Unable to change hostnameReview server-side errors and the actual current hostname before retrying.
Hostname changed but the new URL does not workCheck DNS, certificate coverage, the panel port and service configuration independently. A successful system change does not complete those tasks.

To reverse a successfully applied unintended change, submit the previously recorded valid hostname and verify it. There is no automatic rollback button. Any separate DNS, PTR or certificate changes require their own recovery steps.

Do’s and don’ts

  • Do keep the system hostname and its intended DNS/PTR identity consistent.
  • Do plan for certificates and integrations that still refer to the old name.
  • Do verify the current hostname after a reported success or failure.
  • Do not treat successful format validation as proof that DNS is configured.
  • Do not assume clicking the current-name link tests WAP or every hosting service.
  • Do not confuse changing this server identity with changing a hosting account's primary domain.

Previous: Change Root Password. Next: Resolver Configuration.