Choose a valid fully qualified name such as server1.example.com. Review applications that depend on the existing hostname, including mail software, certificates and hosting panels. Record the old value and confirm you can use the console if remote access is disrupted.

1. Open List VPS > Manage for the correct server.
2. Go to Settings > Change Hostname and enter the approved name without a protocol, space or directory path.
3. Save the change and read the panel response. Application inside the guest depends on its supported template or guest integration.
4. If a restart is required, arrange a maintenance window and restart cleanly. If the provider requires a full stop and start, follow that instruction instead of repeatedly issuing reboots.
5. Inside the guest, check the actual hostname and any relevant hosts-file entry. Configure public DNS and reverse DNS separately through the appropriate authorized systems.

Confirm the panel label and operating-system hostname match the intended setup. Test services that refer to the name and verify certificates still cover the names customers use.

If the panel value changes but the guest does not, ask support about template integration or use the operating system supported hostname-management method. A hosting panel may require its own hostname workflow. Restore the previous value if a dependent service fails, then plan the DNS, certificate and application changes together.

• Checking RAM, storage, IP addresses and virtualization in Virtualizor
• Opening the Virtualizor VNC console
• Restarting a Virtualizor VPS safely
• Checking whether a Virtualizor VPS is running

• Virtualizor: Change Hostname