Debian 12 – resolv.conf Keeps Reverting and DNS Fails – Resolver Control

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

DNS lookups intermittently fail and resolv.conf repeatedly changes after interface renewals.

Environment & Reproduction

Seen when DHCP client scripts, resolvconf, or systemd-resolved compete on Debian 12 nodes.

Root Cause Analysis

Multiple resolver managers write conflicting nameserver data and search domains to resolv.conf.

Quick Triage

Determine current resolv.conf owner and active resolver service before editing files manually.

Step-by-Step Diagnosis

Trace symlink targets, inspect DHCP hooks, and validate active DNS servers with dig tests.

Solution – Primary Fix

Select a single resolver stack, disable competing writers, and enforce nameserver policy centrally.

Solution – Alternative Approaches

Use static resolver entries for isolated hosts where DHCP-provided DNS is unnecessary.

Verification & Acceptance Criteria

resolv.conf remains stable and forward and reverse lookups succeed across reboots and renewals.

Rollback Plan

Re-enable prior resolver service if application behavior depends on previous local DNS caching.

Prevention & Hardening

Document resolver ownership and enforce host baseline checks for DNS stack drift.

Related Errors & Cross-Refs

Temporary failure in name resolution, SERVFAIL spikes, and stale resolver configuration issues.

Related tutorial: View the step-by-step tutorial for Debian 12.

View all Debian 12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian resolvconf, systemd-resolved, and isc-dhcp-client integration references.