Scenario
One namespace sees intermittent traffic to an old service IP after DNS cache rollout.
A NodeLocal DNSCache rollout completes and one namespace still resolves stale service IPs because conntrack pins the old tuple on one node
DNS answers are current, but one node keeps forwarding packets through a conntrack entry built from the previous service IP.
What to check first
- Identify the primary failure signal in the The Address Book Was Updated and One Mail Carrier Kept Delivering Letters Using the Route It Had Memorized Before the Street Was Renumbered scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect conntrack before restarting cluster DNS.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field