Debian Hostname Configuration

Hostname is a critical system identifier that helps distinguish devices in a network. Proper configuration ensures seamless communication, service identification, and log management. Below are key methods to manage hostname in Debian:

1. View Current Hostname

Use any of these commands to check the current hostname:

• hostnamectl status (shows detailed info including static/dynamic hostname)
• hostname (returns the short hostname)
• cat /etc/hostname (displays the persistent hostname stored in the file).

2. Temporary Hostname Change

For immediate but non-persistent changes (resets after reboot), use:

sudo hostname new-hostname

This updates the runtime hostname but does not modify configuration files.

3. Permanent Hostname Change

To make the change permanent across reboots, update the following files:

a. Update /etc/hostname

Edit the file using a text editor (e.g., nano):

sudo nano /etc/hostname

Replace the existing hostname with the new one (e.g., my-debian-server) and save the file. This file stores the persistent hostname.

b. Update /etc/hosts

Modify the /etc/hosts file to map the new hostname to the loopback IP (127.0.0.1 or 127.0.1.1 for Debian):

sudo nano /etc/hosts

Find the line starting with 127.0.1.1 (or 127.0.0.1) and replace the old hostname with the new one. Example:

127.0.0.1   localhost
127.0.1.1   my-debian-server

Save the file. This ensures the system resolves the hostname to the correct IP locally.

c. Restart Hostname Service (Optional)

To apply changes without rebooting, restart the systemd-hostnamed service:

sudo systemctl restart systemd-hostnamed

4. Alternative: Using hostnamectl for Permanent Change

The hostnamectl command can also set a permanent hostname directly:

sudo hostnamectl set-hostname new-hostname

This updates both /etc/hostname and /etc/hosts automatically. No additional steps are required.

Debian Network Configuration

Network setup in Debian involves configuring IP addresses, gateways, and DNS servers. The method depends on your Debian version and preferred network manager.

1. Traditional Method: /etc/network/interfaces

This is the classic approach for Debian versions prior to 10 (Stretch) and remains valid for later versions (with ifupdown2).

Steps:

1. Backup the existing configuration:

   sudo cp /etc/network/interfaces /etc/network/interfaces.bak
   

2. Edit the file:

   sudo nano /etc/network/interfaces
   

3. Configure the interface (replace eth0 with your actual interface name, e.g., ens33):
   • Static IP:

     auto eth0
     iface eth0 inet static
         address 192.168.1.100
         netmask 255.255.255.0
         gateway 192.168.1.1
         dns-nameservers 8.8.8.8 8.8.4.4
     

   • DHCP:

     auto eth0
     iface eth0 inet dhcp
     

4. Restart the networking service:

   sudo systemctl restart networking
   

5. Verify connectivity:

   ping -c 4 google.com
   ```.  
   
   
   

2. Modern Method: netplan (Debian 10+)

Debian 10 (Buster) and later use netplan for network configuration.

Steps:

1. Create or edit a netplan YAML file (e.g., /etc/netplan/01-netcfg.yaml):

   sudo nano /etc/netplan/01-netcfg.yaml
   

2. Add configuration (replace eth0 with your interface name):

   network:
     version: 2
     renderer: networkd
     ethernets:
       eth0:
         dhcp4: no
         addresses: [192.168.1.100/24]
         gateway4: 192.168.1.1
         nameservers:
           addresses: [8.8.8.8, 8.8.4.4]
   

   For DHCP, set dhcp4: yes and remove the addresses, gateway4, and nameservers sections.
3. Apply the configuration:

   sudo netplan apply
   

4. Verify connectivity as above.

3. NetworkManager (Desktop Environments)

For desktop environments (e.g., GNOME, KDE), NetworkManager provides a graphical interface and CLI tools.

Steps (CLI):

1. List available connections:

   nmcli connection show
   

2. Modify an existing connection (replace Wired connection 1 with your connection name):

   sudo nmcli connection modify "Wired connection 1" ipv4.method manual ipv4.addresses 192.168.1.100/24 ipv4.gateway 192.168.1.1 ipv4.dns "8.8.8.8,8.8.4.4"
   

3. Restart the connection:

   sudo nmcli connection down "Wired connection 1" && sudo nmcli connection up "Wired connection 1"
   

4. For GUI, click the network icon in the top panel, select “Edit Connections,” and configure the desired interface.

Key Notes on Hostname-Network Relationship

• DNS Resolution: The hostname must be resolvable to an IP address (via /etc/hosts or a DNS server) for other devices to access it.
• Service Identification: Web/mail servers use the hostname in SSL certificates and email headers—incorrect settings can cause connection failures.
• Logs and Scripts: System logs and automation scripts rely on the hostname to identify the source of events or tasks.