A county lookup of a Service DNS name fails inside a Pod before any TCP connection is attempted. Where should triage start?
Select an answer to reveal the explanation.
Short Explanation
If the name never resolves, you’re still in the phonebook chapter—check CoreDNS before blaming the highway. DNS failures and TCP refusals are different villains.
Full Explanation
Failure to resolve a Service name is a DNS-plane problem. Administrators should verify CoreDNS health, configuration, and expected Service DNS records before changing CNI wholesale, targetPort values, or deleting NetworkPolicies. Separating DNS from connect-time failures speeds correct remediation.