π ~1 min read
Table of contents
Symptom & Impact
Name lookups randomly fail while direct IP connectivity still works.
Environment & Reproduction
Test with `dig`, `resolvectl query`, and `nmcli device show` to inspect active DNS servers.
Root Cause Analysis
Confirm resolver-related packages and NetworkManager plugins are present via dnf.
Quick Triage
Check `systemctl status NetworkManager` and any local caching resolver service units.
Step-by-Step Diagnosis
Use `journalctl -u NetworkManager –since -2h` for DNS update race or timeout messages.

Solution – Primary Fix
Capture effective `/etc/resolv.conf` management mode and profile DNS settings.
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
Verify UDP/TCP 53 path and firewall policy between host and DNS servers.
Verification & Acceptance Criteria
Review AVC denials if local DNS proxy processes fail to read config or bind sockets.
Rollback Plan
Pin stable DNS servers in connection profile and restart affected network services.
Prevention & Hardening
Run repeated lookup loop tests and confirm no timeout spikes.
Related Errors & Cross-Refs
Deploy redundant resolvers and monitor DNS latency with service-level alerts.
Related tutorial: View the step-by-step tutorial for rhel-9.
View all rhel-9 tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Provide packet captures, resolver logs, and profile exports for analysis.
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.