yum Cannot Resolve Repository Hostnames

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

yum fails because repository domains cannot be resolved.

Environment & Reproduction

Errors include Could not resolve host and metadata download failures.

Root Cause Analysis

Incorrect /etc/resolv.conf, DNS outages, or blocked egress through firewalld cause lookup failures.

Quick Triage

Verify interface state with systemctl or service networking status and test name resolution.

Step-by-Step Diagnosis

Use ping, host, nslookup, yum repolist, firewall-cmd on firewalld, and journalctl -u network.

Solution – Primary Fix

Set valid DNS servers, restart network service with systemctl, allow outbound traffic in firewalld, then run yum clean all and yum makecache.

Solution – Alternative Approaches

yum repolist and yum update should complete with no hostname errors.

Verification & Acceptance Criteria

Restore previous resolver configuration if custom DNS introduces regressions.

Rollback Plan

Use redundant resolvers and monitor DNS failures in journalctl.

Prevention & Hardening

Deploy resolver templates through config management before scheduled yum maintenance.

Related Errors & Cross-Refs

Legacy ifcfg scripts and NetworkManager can conflict if both are managed inconsistently.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Escalate when upstream DNS and proxy layers are controlled by another team.