How to Fix Failed to Start Update resolvconf in Ubuntu

During startup or network interface reloads on Ubuntu Linux systems, administrators may encounter a highlighted red systemd error: [FAILED] Failed to start Update resolvconf for network changes, or see the unit resolvconf.service marked as failed in systemctl. In modern Ubuntu releases, conflict between legacy resolvconf packages and the native systemd-resolved daemon frequently causes this service unit to crash or enter infinite retry loops. Resolving this discrepancy restores seamless DNS lookups.

Inspect Failed Unit Details and Service Status

To determine why the resolvconf update unit failed to execute, inspect the systemd status log in your terminal:

  1. Check the status of the service:
    systemctl status resolvconf.service
  2. Query the systemd journal for specific execution errors:
    journalctl -u resolvconf.service -b 0
  3. Look for common triggers:
    • /etc/resolvconf/run: No such file or directory: Indicates missing volatile runtime directory mounts under /run/resolvconf.
    • resolvconf: Error: /etc/resolv.conf isn't a symlink: Indicates that /etc/resolv.conf is a static file rather than the expected symbolic link.
    • Failed to pull resolved DNS settings: Points to an incompatible bridge script between systemd-resolved and resolvconf.

Restore the Correct Symbolic Link for /etc/resolv.conf

A static /etc/resolv.conf file prevents resolvconf and systemd-resolved from writing dynamic DNS entries:

  1. Inspect the current status of the file:
    ls -l /etc/resolv.conf
  2. If the output indicates a standard file instead of a symlink (-rw-r--r--), back up the existing configuration:
    sudo cp /etc/resolv.conf /etc/resolv.conf.bak
  3. Remove the static file:
    sudo rm -f /etc/resolv.conf
  4. Create the proper symlink pointing to the systemd-resolved dynamic runtime stub:
    sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
  5. Restart the resolver service:
    sudo systemctl restart systemd-resolved

Reconfigure or Purge the Obsolete resolvconf Package

Ubuntu 20.04, 22.04, and 24.04 use systemd-resolved as their primary DNS manager. If the legacy resolvconf package was manually installed by older VPN or networking scripts, it creates an ongoing conflict:

  1. If you don’t specifically require legacy resolvconf hooks for legacy PPPoE or dial-up configurations, purge the conflicting package cleanly:
    sudo apt purge resolvconf
  2. Reload the systemd daemon:
    sudo systemctl daemon-reload
  3. If you must retain the package for specific VPN client compatibility (e.g. older OpenVPN configurations), reinstall and reconfigure its runtime directories:
    sudo apt install --reinstall resolvconf
    sudo dpkg-reconfigure resolvconf

Create Missing Volatile Runtime Directories via tmpfiles.d

If resolvconf.service fails because /run/resolvconf is missing on fresh system boots:

  1. Create a dedicated configuration file inside systemd’s tmpfiles directory:
    sudo nano /etc/tmpfiles.d/resolvconf.conf
  2. Add the following directory creation directive:
    d /run/resolvconf 0755 root root -
    d /run/resolvconf/interface 0755 root root -
  3. Save and exit the file.
  4. Apply the tmpfiles rules immediately without restarting:
    sudo systemd-tmpfiles --create

Verify Clean DNS Resolution

Once configuration files are refreshed, verify that domain resolution operates correctly across all interfaces:

  1. Test service restart:
    sudo systemctl restart resolvconf.service
  2. Verify that systemd reports zero failed units:
    systemctl list-units --failed
  3. Perform a DNS query test:
    resolvectl status
    ping -c 3 digitash.com
  4. Confirm that ping packets return normal latency and resolution without timeouts.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.