π ~1 min read
Table of contents
Symptom & Impact
Hostname lookups fail intermittently, disrupting package and service access.
Environment & Reproduction
Can appear after VPN, DHCP, or profile changes.
resolvectl query archive.ubuntu.com
ls -l /etc/resolv.conf
Root Cause Analysis
Resolver receives stale or invalid upstream DNS settings.
Quick Triage
Check resolver service state and active DNS servers.
systemctl status systemd-resolved --no-pager
resolvectl status
Step-by-Step Diagnosis
Inspect recent resolver errors and per-link DNS configuration.
journalctl -u systemd-resolved -n 80 --no-pager
resolvectl status

Solution – Primary Fix
Restore correct resolv.conf symlink 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.
sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
sudo systemctl restart systemd-resolved

Solution – Alternative Approaches
Set DNS servers explicitly via netplan for deterministic behavior.
sudo netplan get
Verification & Acceptance Criteria
Queries resolve consistently for external and internal domains.
resolvectl query ubuntu.com
getent hosts archive.ubuntu.com
Rollback Plan
Revert DNS profile changes if internal resolution breaks.
sudo systemctl restart systemd-resolved
Prevention & Hardening
Control DNS order and monitor resolver health after network changes.
resolvectl statistics
Related Errors & Cross-Refs
Related errors include temporary failure in name resolution and DNSSEC validation failures.
Related tutorial: View the step-by-step tutorial for Ubuntu 24.04 LTS.
View all Ubuntu 24.04 LTS tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Ubuntu systemd-resolved and DNS operations references.
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.