Your application asks for api.example.com , CoreDNS looks healthy, and yet DNS request volume jumps by a multiple of outbound HTTP traffic. The surprising part is often not a retry or a bad cache. It is the Pod resolver doing exactly what its search path tells it to do. In a measured glibc run, that one two-dot external name produced eight DNS queries, or ten when the Pod also inherited a node search domain.
This post shows the resolver rule, reproduces the count, and gives you a safe way to decide between a trailing dot, a lower ndots value, and DNS-side improvements. The numbers below are a controlled resolver experiment, not a promise about every language runtime.
TL;DR
Kubernetes documents ndots:5 and a three-part Service search list for a normal Linux Pod. A name with fewer than five dots is searched under those suffixes before glibc tries it as absolute.
In our glibc 2.36 measurement, api.example.com generated eight A and AAAA queries with three search suffixes.…