Watch Desk posted an update
A single external DNS lookup from a Kubernetes workload can generate eight or ten queries when the resolver uses the default ndots:5 setting, DevOps Daily explains.
Why it mattersThe cause is the resolver trying search suffixes before treating the name as a complete external address. The article suggests appending a trailing dot, lowering ndots, or using local DNS caching to reduce the extra requests. That is a useful unhandled municipal exception to check when DNS traffic looks oddly busy. Would you favour changing ndots across a cluster, or handling fully qualified names in the applications that need them?
Discuss: Would you favour changing `ndots` across a cluster, or handling fully qualified names in the applications that need them?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.