The Connectivity Purge Vector
When an Ubuntu server mysteriously drops its static IP address, fails to resolve DNS queries, or becomes trapped in a continuous, failed DHCP handshake loop, simply unplugging the Ethernet cable is insufficient. The network configuration daemon running in the system’s RAM is corrupted. You must not reboot the entire physical server—which causes unnecessary downtime for web applications—but instead execute a surgical command to instantly terminate and restart the specific `NetworkManager` service.
How to Restart the Network
Modern Ubuntu deployments utilize `systemd` as the master initialization architecture. You must use the `systemctl` command to forcefully reboot the networking daemon without affecting the rest of the kernel.
1. Open your terminal application or connect to the server via SSH.
2. The Execution Command (`systemctl`):
* Because you are manipulating a core system service that controls all incoming and outgoing data, you must possess root privileges.
* Type the following exact command:
sudo systemctl restart NetworkManager
* Press Enter and provide your administrative password.
3. The Handshake Interruption:
* If you are executing this command via an active SSH connection, your terminal will likely freeze for 3 to 10 seconds. This is normal. The command violently severs your own connection, rebuilds the networking stack, and re-establishes the SSH tunnel almost instantly.
* When the prompt returns, the execution is complete.
4. Verification (The Status Check):
* You must mathematically verify that the daemon successfully rebooted and is not trapped in an error state.
* Type: sudo systemctl status NetworkManager
* Press Enter.
* Look for the text `Active: active (running)`. Directly below that, look at the timestamp (e.g., `since Tue 2026-10-06 14:32:10 UTC; 15s ago`). If the timestamp confirms it started seconds ago, the reboot was successful.
* Press q to exit the status screen.
5. Legacy Override (Older Ubuntu Versions):
* If you are operating a highly obsolete Ubuntu server (16.04 or older) that predates `systemd`, the previous command will fail. You must use the legacy initialization script.
* Type: sudo service network-manager restart