← Problem Library
K8s L4 K8S 1516 · 9 min

A CoreDNS change is applied and one namespace still resolves stale IPs because NodeLocal DNSCache kept the old conntrack tuple alive

DNS answers are correct in CoreDNS, but one node-local cache path still returns older service endpoints.

K8sPlatform ReliabilityLevel 4Pro9 min
Scenario

Only one namespace behind one node-local cache keeps seeing stale service IPs after a CoreDNS update.

What to check first
  • Identify the primary failure signal in the The Cluster Learned the New Address and the Neighborhood Resolver Kept Repeating the Number It Had Already Memorized scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect node-local cache state before restarting CoreDNS globally.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.