📖 ~1 min read
Table of contents
Symptom & Impact
Resolvers stay unchanged, causing failed package downloads and service discovery timeouts.
Environment & Reproduction
Most common on DHCP interfaces where profile and runtime state diverge.
nmcli dev show | grep -E 'IP4.DNS|GENERAL.CONNECTION'
Root Cause Analysis
Connection profile settings are overridden by DHCP or stale resolv.conf ownership behavior.
Quick Triage
Check active profile, dispatcher scripts, and DNS priority settings.
sudo journalctl -u NetworkManager --since -1h
Step-by-Step Diagnosis
Inspect ipv4.ignore-auto-dns and verify if systemd-resolved integration is active.
nmcli con show

Solution – Primary Fix
Set static DNS in profile, disable auto DNS for that connection, then reconnect.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
sudo nmcli con mod ipv4.ignore-auto-dns yes ipv4.dns '1.1.1.1 9.9.9.9' && sudo nmcli con up

Solution – Alternative Approaches
Set DNS via DHCP server reservations or use split DNS with local caching resolver.
Verification & Acceptance Criteria
dig and host queries resolve through expected nameservers after reconnect/reboot.
Rollback Plan
Re-enable auto DNS and restore previous connection profile values.
Prevention & Hardening
Manage NetworkManager profiles declaratively and monitor DNS drift with periodic checks.
Related Errors & Cross-Refs
Related: resolv.conf immutable bit, DNSSEC validation failures, and search domain misconfiguration.
Related tutorial: View the step-by-step tutorial for oracle-linux-10.
View all oracle-linux-10 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
RHEL networking and NetworkManager DNS behavior documentation.
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.