← Problem Library
K8s L6 K8S 1481 · 12 min

A Cilium FQDN policy looks updated and pods still fail because the DNS proxy keeps the old wildcard until the cache TTL outlives the policy revision

The new domain rule is present, but the proxy still evaluates traffic against the previous wildcard answer in cache.

K8sPlatform ReliabilityLevel 6Pro12 min
Scenario

Pods stay blocked after an egress FQDN rule is tightened even though the updated policy is visible on the node.

What to check first
  • Identify the primary failure signal in the The Policy Learned the New Name and the DNS Proxy Kept Trusting the Last One It Heard 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

Compare policy revision timing and DNS proxy cache before widening egress again.

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.