How to Troubleshoot Kubernetes Applications That Cannot Resolve Service Names

In-cluster DNS failures can result from CoreDNS health, search domains, network policy, or incorrect service naming.

Checks to make

Test resolution from the affected pod, check namespace and fully qualified service name, inspect CoreDNS pods and logs, and review network policy. Compare a known-good workload and avoid changing cluster DNS globally before isolating the failure.

When to get help

Kubernetes operations can trace service discovery and cluster DNS. Informatix Systems can assess the symptoms, evidence, and next steps. Contact Informatix Systems to discuss this issue.