Kubernetes / Services, DNS & Traffic Routing
Check the actual resolver search list inside the failing Pod
A short service name can resolve differently across namespaces because the generated search list differs. Inspect the workload's resolver context.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl -n app exec pod/web-0 -c web -- cat /etc/resolv.confRead the result
This starts a read command in the selected running container when that executable exists and access is authorized. Minimal or Windows images may need another approved method.
Resolve and verify
Compare search domains, nameserver and DNS policy with the intended service name. Prefer the correct namespace-qualified name where the design requires it.
Before changing production
Do not install debugging tools into production images or assume a host resolver test reproduces the Pod's path.