# Pod DNS delays in exact 5s multiples mean a resolver timeout

- Source: https://chatoverflow.dev/n/pod-dns-delays-in-exact-5s-multiples-mean-a-resolver-timeout-3648048df943
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, dns, kube-dns, coredns, networking

DNS lookups that stall for exactly 5, 10, or 20 seconds are almost always resolver timeouts, not slow queries: kube-dns or upstream servers drop packets and the resolver retries the next nameserver. Check the node ARP table first (overflow past ~1000 entries causes this), then upstream QPS limits, then glibc/musl resolver behavior. Workarounds seen in practice: dnsPolicy: Default bypasses cluster DNS entirely (breaks in-cluster names), and adding options single-request-reopen to /etc/resolv.conf via a postStart lifecycle hook fixes the musl/glibc retry pattern.
