DNS ndots:5 — 10 queries and 8 NXDOMAINs for one resolution

DNS ndots:5 — 10 queries and 8 NXDOMAINs for one resolution A sequence diagram generated by Archify. 0.00 ms · A + AAAA in parallel · sts.ap-northeast-2.amazonaws.com.bench-net.svc.cluster.local. NXDomain ×2 (0.92 / 1.14 ms) — kubernetes plugin, authoritative 1.21 ms · A + AAAA · sts.ap-northeast-2.amazonaws.com.svc.cluster.local. NXDomain ×2 (2.01 / 2.26 ms) 2.32 ms · A + AAAA · sts.ap-northeast-2.amazonaws.com.cluster.local. NXDomain ×2 (3.15 / 3.41 ms) 3.47 ms · A + AAAA · sts.ap-northeast-2.amazonaws.com.ap-northeast-2.compute.internal. forward . /etc/resolv.conf — outside the cluster.local zone, so upstream NXDomain (non-authoritative) NXDomain ×2 (3.68 / 3.93 ms) 3.99 ms · A + AAAA · sts.ap-northeast-2.amazonaws.com. forward . (upstream lookup on a cache 30 miss) — not captured by the pod-side tcpdump A 10.0.3.84 · A 10.0.2.129 — STS interface endpoint, one ENI per AZ 4.37 ms · A 10.0.3.84, A 10.0.2.129 · AAAA no data — answer in the last 0.38 ms A + AAAA in parallel · sts.ap-northeast-2.amazonaws.com. forward . (upstream lookup on a cache 30 miss) — not captured by the pod-side tcpdump A 10.0.3.84 · A 10.0.2.129 A ×2 · AAAA no data ndots:5 — sts.ap-northeast-2.amazonaws.com (3 dots < 5) · 4 search suffixes walked first · 10 queries · 8 NXDOMAIN · 4.37 ms end-to-end (warm median 3.78 ms) trailing dot — sts.ap-northeast-2.amazonaws.com. (absolute name) · no search walk · 2 queries · 0 NXDOMAIN · warm median 0.80 ms Pod app (glibc 2.41) · Sequence participant Pod app (glibc 2.41) CoreDNS 172.20.0.10 · Sequence participant CoreDNS 172.20.0.10 VPC resolver · Sequence participant VPC resolver Legend request (A + AAAA) answer upstream forward next candidate