The node-local-dns functions as a NodeLocal DNSCache add-on for clusters. This add-on runs in a DaemonSet on each node in the cluster, working as a DNS cache proxy on nodes to improve the performance and stability of DNS service discovery in the cluster.

DNS cache configuration is injected into pods as soon as the node-local-dns add-on is deployed in the cluster. In this case, the pods have two DNS configurations for round-robin DNS resolution.

NodeLocal DNSCache configuration: The Pod first accesses the DNS cache configuration (169.254.20.10) of the current node. If the configuration is inaccessible, the Pod then accesses the CoreDNS configuration of the cluster.

CoreDNS configuration: The global DNS configuration of the cluster.

Issue description

After you deploy the node-local-dns add-on, check whether the Pods use the local cache of the nodes.

Solution

You can log in to the Pods in the cluster and use the dig command to view the DNS resolution result. When the DNS server is shown as 169.254.20.10, it indicates that the current Pod is using the node-local-dns cache of the node where it is located.

Last updated: 2026.07.23 14:31:46

Public security network record in Beijing: No. 11010802032137