Skip to main content

Manage system hostname with hostnamectl

This article explains the simplest method to set hostname and Fully Qualified Domain Name (FQDN/fqdn) of any given system using hostnamectl

Check that hostnamectl is present on the system by typing it in a shell. You will see output similar to the one given below.


In case hostnamectl is not found, it is a good idea to install it.
sudo apt update
sudo apt install systemd-services

Verify the static hostname given above using the following command:


Also verify it by checking /etc/hostname file


Change the hostname and set the desired hostname by running the following command and authenticating with the password.

hostnamectl set-hostname <hostname>


Start a new shell session or reconnect to the server to see the change in the hostname


Again run above steps to verify that hostname has been changed correctly.

Configure FQDN

While the above process may suffice to identify the host in the local network, it is not enough when the host is to be identifies uniquely over the internet.

For example, here we have setup the hostname as "vm-3". However there may be many such "vm-3" on the internet. Then how to identify our "vm-3" uniquely? For that we need to also add the domain and the top-level-domain (tld), if any, of the network in which the server resides.

FQDN = [hostname].[domain].[tld]

For demo purposes, we are using domain as "shodh" and tld as "demo".

Therefore, the FQDN of the demo server is vm-3.shodh.demo

Let's add this FQDN to the server.

Edit the /etc/hosts file and add FQDN in front of hostname as shown below.
FORMAT: <ip> <fqdn> <hostname>


Test the FQDN setup as follows:


That's it folks! We have successfully setup the hostname and the FQDN for our server.

Comments

Popular posts from this blog

Using static IPs in Linux

It is often a requirement to assign static IP addresses to some important and permanent network interfaces. This is to avoid setting up a local DHCP server or relying on IP given by your network provider which may not be stable. This post shows steps to configure static IPs in Linux using Ubuntu 16.04 and Ubuntu 18.04 distros. We are considering two distros as network configuration has changed significantly in Ubuntu 18.04. There are two general steps to be followed: 1. Configure the network interface and assign a static IP. 2. Restart interface for the changes to take effect. Ubuntu 16.04  The current interfaces on the system are as follows: As can be seen, enp0s8 interface does not have any IP. Let's assign a static IP to it. In case you already have an interface with a DHCP assigned IP, you just need to change that IP and make it static. Edit the /etc/network/interfaces file and add the following code block. Prefer using the IP address range available for pri...

Simple HTTP Server in Python

Have you ever come across a need to share a file over a local network to a number of machines? Have you ever felt the need to share output of a task in text files available at a web-endpoint? Often, there is a requirement to quickly setup a light-weight web-server for such requirements. Python provides the easiest way to setup a simple HTTP server for such use cases with a single command. Python comes pre-installed with Linux as many of the linux libraries use python in background. Therefore there is no extra overhead of installing python. With support for python2 getting stopped in April 2020, many of the newer versions of linux distros come with default python3. Therefore this post will focus on setting up an HTTP server using both python2 and python3. We will be using Ubuntu 16.04, however it will work for majority of the linux systems where python comes pre-installed. Preparation Steps to follow before starting the server: Make sure you are in the directory which you want ...

Local domain name resolution using /etc/hosts

The /etc/hosts file is a powerful mechanism for managing the information about hosts in the local network in the absence of a local DNS server. Setup We have 4 VMs in the local /24 network. The following are the details: vm-1-ubuntu-16-04 - 10.0.1.11 vm-2-ubuntu-16-04 - 10.0.1.12 vm-1-ubuntu-18-04 - 10.0.1.21 vm-2-ubuntu-18-04 - 10.0.1.22 The VMs are reachable via their IP address but not by their hostnames. This is problematic because we have to remember their IP addresses everytime we want to access these hosts. It is would be much simpler to remember and access the servers by their hostnames. For that we need some sort of mapping between the IP addresses and their corresponding host names. There are 3 common ways of achieving this mapping. Setup a DNS server which handles resolution for your local network. Use an existing DNS server of the local Internet Service Provider (ISP) or any other higher level ISP. Note that a public static IP address is required for this s...