
A hostname is a name that is given to a system within a network to uniquely identify it among other devices. It serves as a human-readable label that simplifies communication, troubleshooting, and management. Instead of remembering IP addresses, administrators and users can reference machines using recognizable names like web01, db-server, or node1.example.com.
Hostname are important for:
Changing the hostname is a common task when setting up new servers, applying naming conventions, or preparing systems for production environments.
Changing the hostname using the Vultr Console triggers a full server reinstall because it uses cloud-init to set the hostname during provisioning. This process erases all data on the server, including the operating system and files.
Follow this guide to change the hostname on CentOS, Fedora, FreeBSD, Ubuntu, and Windows Server without reinstalling the server or losing any data.
Before you begin, you need to:
To make your hostname changes permanent, remove the hostname related directives from the /etc/cloud/cloud.cfg file. This prevents cloud-init from resetting the hostname on reboot.
Open the /etc/cloud/cloud.cfg file using an test editor.
Locate the cloud_init_modules section and remove the following directives.
Save and close the file.
Follow the steps below to change the hostname on RHEL-based distros like CentOS or Fedora.
View the hostname of your server.
Your output should be similar to the one below:
Change the server hostname by running the following command.
Replace my-new-hostname with the new hostname you want to set.
Update the /etc/hosts file with the new hostname. Also if you have a DNS entry then the best practice is to update the name in this file as well.
After updating, the file should be similar to the one below:
Reboot the server to apply the changes.
Verify that your hostname changes are reflected on the server.
Output:
Verify that your hosts file changes is also reflected.
Your output should be similar to the one below:
In this guide, you changed the hostname across multiple operating systems without reinstalling your server or losing data. You updated the hostname configuration on CentOS, Fedora, FreeBSD, Ubuntu, and Windows Server using system-specific tools and disabled cloud-init to prevent overwrites. These steps ensured the changes persisted across reboots and followed best practices for system administration.
0 Comments
Be the first to comment and share your perspective with the community.