RHEL 9 systemd-resolved DNS lookup delays on servers

📖 ~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

Hostname resolution becomes slow and affects package installs and app startup.

Environment & Reproduction

dig may be fast while system resolver calls delay due to upstream fallback behavior.

Root Cause Analysis

Unreachable nameserver entries, search domain loops, or resolver service misconfiguration.

Quick Triage

Run resolvectl status, cat /etc/resolv.conf, and test direct queries against each server.

Step-by-Step Diagnosis

Check systemctl status systemd-resolved and confirm expected mode on RHEL 9.

Solution – Primary Fix

Review journalctl -u systemd-resolved for retries and unreachable upstream indicators.

Solution – Alternative Approaches

Allow DNS traffic paths and verify no ACL or firewalld rule blocks resolver egress.

Verification & Acceptance Criteria

Reduce unnecessary search suffixes that create repeated failing lookups.

Rollback Plan

Resolver files should retain proper contexts after manual edits or template application.

Prevention & Hardening

Use NetworkManager profiles to enforce known-good resolver ordering.

Related Errors & Cross-Refs

Monitor DNS response times and alert on resolver retry spikes.

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

Confirm low-latency lookups from getent hosts and application-level tests.