π ~1 min read
Table of contents
Symptom & Impact
Host can reach IP addresses but domain lookups fail, breaking package and API access.
Environment & Reproduction
Ubuntu 24.04 LTS using systemd-resolved with /etc/resolv.conf symlink management.
Root Cause Analysis
Broken resolv.conf symlink, unreachable upstream DNS, or stale per-link resolver state.
Quick Triage
Check resolvectl status, resolvectl query ubuntu.com, and symlink target of /etc/resolv.conf.
Step-by-Step Diagnosis
Inspect systemd-resolved logs, link-specific DNS config, and firewall rules for UDP and TCP port 53.
Solution – Primary Fix
Restore /etc/resolv.conf symlink to /run/systemd/resolve/stub-resolv.conf and 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
Set static nameserver entries in netplan for servers where local resolver is intentionally bypassed.
Verification & Acceptance Criteria
resolvectl query and dig commands resolve external domains reliably.
Rollback Plan
Revert resolver configuration changes and reload previous network profile.
Prevention & Hardening
Use redundant DNS servers and monitor query latency and failure rates.
Related Errors & Cross-Refs
proxy DNS interception and split-horizon DNS policies can mimic resolver outages.
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 DNS troubleshooting references and systemd-resolved manual pages.
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.
