🟠 High   ⏱ 5–30 min  Last verified: 19 May 2026
Affected versions: Ubuntu 26.04 LTS

πŸ“– ~1 min read

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution – Primary Fix
  7. Solution – Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

Hosts cannot resolve domain names, breaking package updates and outbound service calls.

Environment & Reproduction

Appears after network profile changes or DNS server outages.

resolvectl status
ping -c 2 google.com
sudo apt update

Root Cause Analysis

Incorrect upstream DNS servers, stale link settings, or resolver service instability.

Quick Triage

Confirm local resolver health and test direct upstream resolution.

systemctl status systemd-resolved
resolvectl query ubuntu.com
getent hosts archive.ubuntu.com

Step-by-Step Diagnosis

Trace DNS path from local stub to configured upstream servers.

cat /etc/resolv.conf
resolvectl dns
resolvectl statistics
journalctl -u systemd-resolved -n 100
Illustrative mockup for ubuntu-26-04-lts β€” terminal_or_shell
DNS and resolver diagnostics β€” Illustrative mockup β€” Progressive Robot

Solution – Primary Fix

Set valid DNS servers in netplan, apply config, and restart resolver.

Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

sudoedit /etc/netplan/01-netcfg.yaml
sudo netplan generate
sudo netplan apply
sudo systemctl restart systemd-resolved
Illustrative mockup for ubuntu-26-04-lts β€” logs_or_journal
resolved service logs for name lookup failures β€” Illustrative mockup β€” Progressive Robot

Solution – Alternative Approaches

Temporarily set per-interface DNS using resolvectl for emergency recovery.

sudo resolvectl dns eth0 1.1.1.1 8.8.8.8
sudo resolvectl flush-caches

Verification & Acceptance Criteria

Name resolution succeeds consistently for internal and external domains.

resolvectl query security.ubuntu.com
ping -c 2 security.ubuntu.com
sudo apt update

Rollback Plan

Reapply previous netplan configuration if new DNS values cause routing policy issues.

sudo cp /etc/netplan/01-netcfg.yaml.bak /etc/netplan/01-netcfg.yaml
sudo netplan apply

Prevention & Hardening

Standardize DNS settings in infrastructure automation and monitor resolver health.

systemctl is-enabled systemd-resolved
resolvectl statistics

Frequently overlaps with VPN DNS leaks, split-horizon misconfiguration, and proxy failures.

Related tutorial: View the step-by-step tutorial for Ubuntu 26.04 LTS.

View all Ubuntu 26.04 LTS tutorials on the Tutorials Hub β†’

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu networking and systemd-resolved documentation for DNS troubleshooting.

Need Expert Help?

If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today β€” we respond within one business day.