Kubernetes / Services, DNS & Traffic Routing
Check cluster DNS component health before editing its configuration
Many applications can fail together when cluster DNS is unavailable, but network policy or upstream forwarding may be the real issue.
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 kube-system get pods -l k8s-app=kube-dns -o wideRead the result
This common label identifies DNS Pods on many clusters; distribution-specific labels may differ. Running Pods do not prove successful DNS responses.
Resolve and verify
Compare readiness, recent DNS logs and Service endpoints with the failing query path. Repair the demonstrated component or upstream dependency through the cluster owner.
Before changing production
Do not replace the DNS ConfigMap or restart every system Pod without preserving evidence and the supported configuration.