⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 96 of 135 in Linux & SRE
Junior / Associate DevOps [L1] Linux Linux / SRE — Scenario-Based Interview Questions Core Fundamentals [L1]
🎯 Target Role / Context: Linux Scenario #56 (L1) · Linux / SRE — Scenario-Based Interview Questions

Q: A developer adds an entry to `/etc/hosts` to override DNS for testing, but it doesn't seem to work. DNS still resolves the original IP. What could be wrong?

The /etc/hosts file provides static hostname-to-IP mappings. Whether it takes precedence over DNS is controlled by /etc/nsswitch.conf.

#Linux #L1 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Name resolution order, nsswitch.conf.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Name resolution order, nsswitch.conf.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

The /etc/hosts file provides static hostname-to-IP mappings. Whether it takes precedence over DNS is controlled by /etc/nsswitch.conf.

  • Typo or formatting error: Each line must be IP_ADDRESS hostname [alias], separated by spaces or tabs. Extra characters or wrong formatting silently breaks the entry.
  • Application-level DNS caching: Some applications (Java, browsers) cache DNS lookups internally and ignore /etc/hosts changes until restarted.
  • systemd-resolved: Modern distributions may route DNS through systemd-resolved, which may have its own caching. Flush with resolvectl flush-caches.
2️⃣

Remediation & Permanent Safeguards

Check the hosts: line in /etc/nsswitch.conf: This means the system checks /etc/hosts first (files), then DNS. If the order is reversed (hosts: dns files), DNS takes priority and /etc/hosts is only consulted if DNS fails. Other common issues:

hosts: files dns
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Typo or formatting error: Each line must be IP_ADDRESS hostname [alias], separated by spaces or tabs. Extra characters or wrong fo."
⚡ 60-Second Elevator Pitch Talking Points
  • Typo or formatting error: Each line must be IP_ADDRESS hostname [alias], separated by spaces or t...
  • Application-level DNS caching: Some applications (Java, browsers) cache DNS lookups internally an...
  • systemd-resolved: Modern distributions may route DNS through systemd-resolved, which may have its...
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring developer adds entry SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
  2. Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring developer adds entry Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (df -h) shows ample free space.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring developer adds entry Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
  4. Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring developer adds entry Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (pid_max).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →