DNS is weird inside k8s on AWS

Из ленты dev.to devops — кратко, чтобы не потерять.

A ~6 minute read — just three concepts that, once you know them, change how you reason about DNS inside a cluster. While chasing some DNS timeouts recently, I went down a rabbit hole and came out with three concepts I wish I’d known earlier. None of them is exotic, but together they explain a surprising amount of “why is DNS being weird” behaviour on Kubernetes-on-AWS. ndots — why one hostname lookup can become many DNS queries NodeLocal DNS — the per-node caching layer your queries actually hit first The EC2 per-ENI DNS packet limit — a hard ceiling most people never hear about until they hit it 1. ndots : one lookup is rarely one query Pull /etc/resolv.conf from inside almost any Kubernetes pod and you’ll see three interesting lines: nameserver < cluster - dns > search my - namespace . s

Полный текст и контекст у первоисточника: https://dev.to/harishteens/dns-is-weird-inside-k8s-on-aws-570c