Transit troubleshoots DNS from inside an application Pod and inspects /etc/resolv.conf. What should that file typically show regarding cluster DNS?
Select an answer to reveal the explanation.
Short Explanation
Open /etc/resolv.conf and you should see the cluster DNS Service IP as nameserver, plus those handy search domains. That is how Pods know to ask CoreDNS first for in-cluster names.
Full Explanation
Kubelet configures Pod DNS so /etc/resolv.conf typically lists the cluster DNS Service IP and appropriate search domains (namespace and svc.cluster.local). That steers queries to CoreDNS. Defaulting only to public resolvers, self-referential Pod IPs, or the apiserver VIP as the Service DNS nameserver is incorrect for normal cluster DNS.