CentOS Stream 10 – Common Problem 105 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Name resolution intermittently fails despite reachable interfaces.

Environment & Reproduction

Often after VPN connects, systemd-resolved tweaks, or netplan-like overrides.

Root Cause Analysis

NetworkManager dns plugin clashes with /etc/resolv.conf or resolved.

Quick Triage

Inspect resolvectl status and nmcli connection show dns settings.

Step-by-Step Diagnosis

Capture failures with dig +trace against the configured DNS server.

Solution – Primary Fix

Pin dns=none or dns=systemd-resolved and set per-connection ipv4.dns.

Solution – Alternative Approaches

Use ipv4.dns-priority to enforce ordering across active connections.

Verification & Acceptance Criteria

Lookups succeed via resolvectl query and dig from both stacks.

Rollback Plan

Restore default NetworkManager.conf dns setting if applications regress.

Prevention & Hardening

Document resolver topology in runbooks and managed configs.

Related Errors & Cross-Refs

Often related to mDNS or split-horizon DNS failures.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

NetworkManager-dns and resolved manuals.