⚡ ~/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 Networking & Cloud DNS Interview Questions Scenario 28 of 55 in Networking & Cloud DNS
Senior DevOps / SRE [L2] Networking Production Scenario [L2]
🎯 Target Role / Context: Networking Scenario #28 (L2) · Networking

Q: Users inside the corporate office navigate to `wiki.company.com` and hit the fast, private internal server IP `10.0.5.10`. Users working from a coffee shop navigate to `wiki.company.com` and hit the public AWS Load Balancer IP `203.0.113.1`. How is the same domain name returning two completely different IPs without conflict?

This is achieved via Split-Horizon DNS.

#Networking #L2 #VPC #DNS #Security
🎙️ Candidate Opening & Architectural Context
""Isolating network failures requires proving whether packets are dropped by route tables, security groups, or stateless NACLs. The interviewer is testing: Split-Horizon DNS (Split-brain DNS).. 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? KodeKloud's Istio Service Mesh & Advanced Kubernetes Networking Course covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "Isolating network failures requires proving whether packets are dropped by route tables, security groups, or stateless NACLs. The interviewer is testing: Split-Horizon DNS (Split-brain DNS).. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

This is achieved via Split-Horizon DNS.

  • Internal Zone: The corporate office routers hand out internal DNS servers (like Active Directory DNS or Route 53 Resolver) via DHCP. These servers hold an authoritative internal zone for company.com and return 10.0.5.10.
  • External Zone: The rest of the world queries public DNS resolvers, which traverse to the public authoritative nameservers for company.com (e.g., Route 53 Public Hosted Zone), which returns the public ALB IP 203.0.113.1.
2️⃣

Remediation & Permanent Safeguards

DNS servers are configured to return different answers based on the originating IP address of the requester.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Internal Zone: The corporate office routers hand out internal DNS servers (like Active Directory DNS or Route 53 Resolver) via DHC."
⚡ 60-Second Elevator Pitch Talking Points
  • Internal Zone: The corporate office routers hand out internal DNS servers (like Active Directory ...
  • External Zone: The rest of the world queries public DNS resolvers, which traverse to the public a...
⛔ 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. Confusing ALB 502 Bad Gateway (target connection reset) with 504 Gateway Timeout (upstream response timeout) when configuring Networking Users inside 502 indicates the backend target closed the TCP connection prematurely or returned malformed HTTP, whereas 504 means the target failed to respond before idle timeout.
  2. Setting target deregistration delay to zero instead of allowing connection draining when configuring Networking Users inside Instant target deregistration severs in-flight HTTP requests during auto-scaling scale-in or rolling deployments, causing immediate user-facing drops.
  3. Failing to query CloudWatch ELB metrics (HTTPCode_ELB_5XX vs HTTPCode_Target_5XX) during load balancer outages when configuring Networking Users inside Comparing load balancer generated errors against target generated errors immediately isolates whether the issue lies in the proxy tier or application runtime.
  4. Overlooking Security Group rules on backend EC2/ECS instances that block health check traffic from the ALB when configuring Networking Users inside Target instances must explicitly permit inbound HTTP/HTTPS traffic from the ALB security group on the configured container/application port.
Advertisement
Want more Networking & Cloud DNS scenarios?
Explore our complete collection of scenario-based Networking & Cloud DNS interview runbooks.
Browse All Networking & Cloud DNS Questions →