Netplan on Ubuntu Server: How to Configure Network Interfaces and Static IPs

Understanding Netplan's Role in Ubuntu Server Architecture

Managing networks on Linux-based operating systems used to be a decentralized task, where each distribution used its own configuration files spread across different directories with divergent logic. On Ubuntu Server, this reality changed with the adoption of Netplan, a modern tool that acts as an intelligent translator between what the systems administrator wants and what the operating system executes under the hood.

In practice, this means you write your network instructions in a human-readable text format called YAML, and Netplan takes care of translating those rules to the underlying network subsystem, which is usually systemd-networkd or NetworkManager. This approach decouples configuration intent from the technical complexity of the low-level tool, drastically simplifying server management.

The main advantage of this architecture is mental portability and consistency. Whether you are managing a virtual machine in the cloud or a physical server in your office, the configuration logic remains exactly the same. Netplan reads files located in the /etc/netplan/ directory and applies IP, gateway, DNS, and routing directives in a centralized and predictable manner.

Anatomy of a YAML Configuration File

Working with YAML files requires strict attention to a detail that often frustrates beginners and experienced professionals alike: space indentation. Netplan uses spaces instead of tabs to hierarchically structure network properties, and any alignment error causes the interpreter to reject the configuration entirely.

To illustrate the basic structure, imagine we need to configure a physical network interface with a fixed IP address. The file usually has a descriptive name, such as 01-netcfg.yaml, and begins by declaring the version of the schema used and the family of devices that will receive the instructions, such as Ethernet network cards.

Inside this file, each level of indentation represents a logical block. The root block defines the network, the next level specifies the interface type (like ethernets), and the innermost level details the specific parameters of that network card, identified by its traditional or predictable logical name.

Configuring a Static IP Address in Practice

On servers, dynamic IP address allocation via DHCP is rarely recommended for infrastructure services because you need the server to always be reachable at the same address on the local network. To pin an IP, we disable automatic DHCP on that specific interface and manually declare the network parameters.

Below is a functional example of a Netplan configuration file applying a static IP address, subnet mask, default gateway, and DNS name servers for internet domain resolution:

network:  version: 2  renderer: networkd  ethernets:    eth0:      dhcp4: no      addresses:        - 192.168.1.100/24      routes:        - to: default          via: 192.168.1.1      nameservers:        addresses:          - 8.8.8.8          - 1.1.1.1

In this example, the renderer directive defines that systemd-networkd will do the heavy lifting of applying the rules. The addresses field uses CIDR notation, where /24 represents the 255.255.255.0 subnet mask, indicating how many bits belong to the local network identification.

Applying and Validating Changes Safely

One of the biggest fears when changing network configurations on a remote server is losing SSH access and locking yourself out of the machine. Netplan has built-in safety mechanisms specifically to mitigate this operational risk and ensure the administrator does not irreversibly lose connectivity.

Instead of applying changes permanently right away, you should use the test command, which waits for manual confirmation. If the change drops the network and you lose access, the system automatically rolls back to the previous configuration after a brief period of unresponsiveness.

The recommended operational workflow consists of editing the YAML file, running the test and verification command, and only confirming if connectivity remains intact. This safety net is indispensable in production environments where uptime and resilience are absolute priorities.

Managing Multiple Interfaces and Failure Points

Enterprise environments and edge servers frequently require more than a single network card. Whether to separate management traffic from application traffic, or to create physical redundancy using link aggregation (bonding), Netplan handles these complex topologies with the same syntactic elegance.

To configure multiple interfaces, simply expand the ethernets block or add specific sections for network bridges and VLANs (Virtual Local Area Networks). Each card receives its own set of rules, enabling advanced routing and traffic segmentation based on corporate security policies.

Adopting VLANs through Netplan, for example, allows a single physical interface to process packets from different isolated virtual networks, optimizing hardware usage and reducing operational costs without sacrificing data isolation between different departments or services.

Troubleshooting Common Issues and Failure Diagnostics

Even with planning, syntax errors or hardware incompatibilities can arise during the implementation of new network rules. When Netplan fails to apply a configuration, the first step is to consult the detailed logs generated by the system to identify the exact line that caused the issue.

The systemd-networkd status command provides a complete overview of the current state of each interface, indicating whether it is operational, which IP address was effectively assigned, and whether there are handshake errors or problems with the physical cable connected to the switch.

Maintaining the history of changes in configuration files and using version control tools like Git for files in the /etc/netplan/ directory ensures that any human error can be reversed instantly, minimizing service downtime.

Final Considerations on Network Management in Ubuntu

Netplan has established itself as the standard for network management in the Ubuntu ecosystem, offering a solid bridge between description simplicity and kernel-level execution robustness. Mastering its syntax and validation commands is a fundamental requirement for any infrastructure engineer or systems administrator.

By standardizing how we define IP addresses, routes, and DNS policies, the tool eliminates operational ambiguities and drastically reduces time spent troubleshooting connectivity issues. Investing time in properly understanding Netplan results in more stable, predictable, and scalable servers throughout the infrastructure lifecycle.