π ~1 min read
Table of contents
Symptom & Impact
Hostnames intermittently fail to resolve despite working network link.
Environment & Reproduction
Appears after VPN toggles or conflicting DNS settings from multiple interfaces.
Root Cause Analysis
systemd-resolved receives invalid upstream servers or split DNS conflicts.
Quick Triage
Run resolvectl status and nslookup ubuntu.com.
Step-by-Step Diagnosis
Inspect /etc/resolv.conf symlink target and check journalctl -u systemd-resolved -n 100.
Solution – Primary Fix
Set known DNS in Netplan, apply with sudo netplan apply, then restart resolved: sudo systemctl restart systemd-resolved.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
Solution – Alternative Approaches
Temporarily test with public resolvers to isolate upstream provider issues.
Verification & Acceptance Criteria
resolvectl query succeeds consistently and package downloads resolve quickly.
Rollback Plan
Restore previous Netplan and resolved configuration from backup.
Prevention & Hardening
Standardize DNS policy for VPN and LAN interfaces.
Related Errors & Cross-Refs
Related: temporary failure resolving archive.ubuntu.com.
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
systemd-resolved man pages and Ubuntu networking docs.
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.
