Use authorized server administration with console access. Record the old hostname and identify dependencies such as monitoring, backups, mail HELO, reverse DNS, certificates and external allowlists. Choose a stable fully qualified hostname that is not confused with a customer website.

1. Publish the new hostname address records and confirm they resolve to the intended server. Coordinate sending-IP reverse DNS with the provider when the mail design requires a matching identity.
2. Inspect Webmin Networking > Network Configuration > Hostname and DNS Client, or the supported operating-system hostname tool for this host. Preserve resolver and interface settings; changing the hostname does not require an unrelated IP or gateway change.
3. Set the intended hostname and review relevant local host mappings through the supported interface. Check whether cloud-init or another provisioning system manages persistent hostname values.
4. Run the Virtualmin configuration check and review host-specific settings. Update the hostname certificate through supported SSL configuration after validation is possible.
5. Inspect mail-server identity, monitoring and backup destinations for explicit references to the old name. Update them deliberately rather than performing a blind global text replacement.
6. Open a new panel session at the new HTTPS hostname and test services. Retain the old DNS name temporarily if clients or operational systems still require a planned transition.

No. Hosted domain definitions and their public DNS remain separate. Do not rename customer virtual servers unless that is an independently planned website-domain change.

Confirm the operating system reports the intended hostname, public DNS is correct and the panel presents a matching certificate. Test outbound mail identity when applicable and verify monitoring and backups still connect. Check persistence at the next planned reboot.

If the name reverts, investigate provisioning ownership before repeated manual edits. If mail or TLS fails, inspect the particular service dependency rather than renaming customer virtual servers. Use the recorded before-state to restore the old identity if the coordinated change cannot complete.

• Requesting and renewing a certificate in Virtualmin
• Configuring mail DNS for a Virtualmin domain
• Completing Virtualmin post-install configuration
• Changing PHP limits for one Virtualmin website

• Webmin: Network Configuration
• Virtualmin: How To Add An SSL Certificate
• Virtualmin: Automated