← Problem Library
Network L2 NETWORK-004 · 16 min

DNS resolves on the host but not inside the container

A typical failure that appears when the container runtime's DNS settings and search domains diverge.

NetworkFoundation OpsLevel 2Free16 min
Scenario

A scenario that narrows down the root cause, centered on comparing the name-resolution path of the host and the container, in the situation of DNS resolving on the host but not inside the container.

What to check first
  • Identify the primary failure signal in the DNS Path 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

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

Questions worth viewing together
Why can host and container DNS results differ?

They may use different resolver files, search domains, runtime injection, or network namespaces even on the same node.

What should be compared side by side?

Compare resolver config, search domains, upstream nameserver reachability, and runtime overrides before changing DNS records.