A VPS hostname identifies the guest system. Updating it in SolusVM is separate from changing public DNS, reverse DNS or a website domain, and applications such as hosting panels can have additional hostname requirements.
IN THIS ARTICLE
Prepare for the change
Choose a valid name such as server1.example.com and record the current name. Review mail services, certificates and automation that depend on it. Check that guest tools are installed when your SolusVM image needs them to apply changes.
01 Change a VPS hostname in SolusVM
- Open the correct project and VPS, then locate its hostname setting in the server settings or edit controls exposed to your role.
- Enter the intended fully qualified hostname without a URL scheme, path or spaces. Review the server identifier before saving.
- Apply the change and read the task result. Follow any restart instruction in a planned maintenance window rather than assuming every version applies it immediately.
- Inside the guest, check the effective hostname and relevant local name resolution. A management label change alone is not enough.
- Update public A/AAAA records, reverse DNS and certificates separately through the systems responsible for them. Follow a hosting panel specific hostname procedure where one is installed.
02 Example: separate a server name from its DNS records
If the intended hostname is server1.example.com, record these related but independent values. Replace the example name and documentation address with your assigned service details.
| Setting | Example or check |
|---|---|
| Guest hostname | server1.example.com, applied through the supported OS or hosting-panel method. |
| Forward DNS | An A record for server1.example.com points to the assigned IPv4 address, such as the illustrative 192.0.2.10. |
| Reverse DNS | The address provider controls the PTR record for that IP. |
| TLS identity | Services presenting a certificate need one that covers the intended name. |
Changing only the label in SolusVM does not create those DNS records or replace a mail-service certificate. Verify each dependency through the system that owns it.
How do I verify the VPS hostname?
Confirm the SolusVM value and guest hostname match the intended configuration. Verify affected services, mail identity and monitoring labels. Check persistence after a planned restart when relevant.
If the change does not work
If the guest keeps its old name, inspect guest integration or ask support to review the task. Current SolusVM can restrict hostname changes by role or service state. Restore the previous name if an application fails, then plan the dependent DNS and certificate work before trying again.