How To Set A Static IP Address On Ubuntu: A Comprehensive Configuration Guide

Configuring a static IP address on Ubuntu requires modifying the Netplan configuration files to replace dynamic DHCP assignments with fixed network parameters. This process ensures consistent host accessibility by manually defining the interface, IPv4 address, subnet mask, gateway, and nameserver settings within the YAML-based network abstraction layer.

Pre-Configuration Requirements and Network Planning

Before initiating changes to your network stack, ensure you have root or sudo privileges, as configuration edits require elevated permissions. Incorrectly modifying network files can lead to a complete loss of remote or local connectivity, necessitating physical access to the machine.

• Essential Prerequisites:

  
  
  
  • Sudo access or root user credentials.
  • The name of your network interface (use the ip link command to identify it).
  • A valid static IP address that falls outside the dynamic DHCP range of your router to prevent IP conflicts.
  • The correct subnet mask, typically expressed in CIDR notation (e.g., /24 for 255.255.255.0).
  • The IP address of your default gateway (usually your router).
  • Preferred DNS resolver addresses (such as 8.8.8.8 for Google or 1.1.1.1 for Cloudflare).

• Estimated Execution Time: 10 to 15 minutes.

• Safety Threshold: Always back up the existing configuration file before making edits to enable a quick rollback in case of syntax errors.

Execution of Static IP Configuration via Netplan

Ubuntu 18.04 and later versions use Netplan as the default network management utility. Netplan processes YAML files located in the /etc/netplan directory to configure network interfaces.

Step 1: Identifying the Network Interface

Before applying any settings, you must identify the exact name of the interface you intend to configure. Open your terminal and execute the ip link show command. Look for an interface name like eth0, ens33, or enp0s3. Note this name exactly, as it is case-sensitive and critical for the configuration file.

Step 2: Locating the Netplan Configuration File

Navigate to the /etc/netplan directory by running the cd /etc/netplan command. List the files in this directory using ls. You will typically see a file ending in .yaml, such as 01-netcfg.yaml or 50-cloud-init.yaml.

Step 3: Backing Up and Editing the YAML Configuration

To prevent accidental data loss, copy your existing configuration file using the command sudo cp 01-netcfg.yaml 01-netcfg.yaml.bak. Once backed up, open the original file with a text editor like nano by executing sudo nano 01-netcfg.yaml.

Warning: YAML is extremely sensitive to indentation. Use only spaces, never tabs, to indent your lines. A single misplaced space will cause the network configuration to fail upon application.

Step 4: Defining Static Network Parameters

Within the editor, clear the dynamic dhcp4: true setting and replace it with your static address configuration. Structure your entries as follows: version: 2, renderer: networkd, and then specify your interface name. Under the interface, define addresses as a list, such as 192.168.1.50/24. Define the gateway using the routes key with a to: default via: your_router_ip structure. Finally, define your nameservers under the nameservers key using addresses: [8.8.8.8, 1.1.1.1].

Step 5: Validating and Applying the Configuration

After saving your changes, verify the syntax by running sudo netplan try. This command tests the configuration for potential connectivity issues; if the network becomes unreachable, Netplan will automatically revert to the previous state after a timeout. If the validation is successful, apply the changes permanently by running sudo netplan apply. Confirm the new address by running ip addr show to verify the interface reflects your manual assignment.

Technical Comparison of Network Assignment Methods

Resolving Common Network Configuration Failures

Even with careful configuration, network services may fail to start or reach the internet due to syntax errors or conflicting assignments.

• YAML Indentation Errors: If the configuration fails to apply, the most likely culprit is incorrect spacing. Ensure that each sub-level is indented by exactly two or four spaces relative to the parent header. Use a YAML linting tool to check your file structure if errors persist.
• IP Address Conflicts: If the system is unreachable after applying the setting, you may have assigned an IP that is already in use by another device. Check your router’s DHCP lease table to ensure the chosen static IP is reserved solely for your Ubuntu machine.
• DNS Resolution Failure: If you can ping an IP address (like 8.8.8.8) but cannot browse hostnames (like google.com), your nameservers are likely misconfigured. Verify the addresses listed under the nameservers section of your YAML file and ensure they are reachable.
• Interface Mismatch: If the system reports that the interface does not exist, verify that the name used in the YAML file matches the output of the ip link command exactly. Interfaces can sometimes change names during kernel updates or hardware reconfigurations.

Frequently Asked Questions

How do I revert to DHCP if the static IP is not working?

To revert to DHCP, open your Netplan YAML file, delete the address and gateway blocks, and set dhcp4 to true. Save the file and run sudo netplan apply to refresh the network state.

Can I set multiple IP addresses on a single interface?

Yes, you can define multiple IP addresses by adding them to the addresses list under your interface configuration in the YAML file. Ensure they are comma-separated and follow the CIDR notation format.

Why does my static IP reset after a reboot?

If your changes are not persistent, it is usually because the configuration was applied using the ip command instead of modifying the Netplan YAML files. Always ensure your changes are made in the /etc/netplan directory to ensure they survive a system restart.

Does changing the static IP affect my existing SSH connections?

Yes, changing the IP address will immediately drop any active SSH sessions connected to the old IP. You must reconnect to the server using the new IP address once the configuration is applied.

What is the advantage of using a static IP over a DHCP reservation?

A static IP configured on the OS level provides network autonomy, ensuring the machine remains accessible even if the DHCP server (your router) goes offline. DHCP reservations still rely on the router to assign the IP, whereas a static assignment is handled entirely by the host’s network stack.

Master Your Ubuntu Infrastructure

Achieving precise network control is the first step toward building stable, high-performance Linux servers and workstations. If you require further assistance with network optimization or advanced routing, consult our internal knowledge base for more specialized administration tutorials.