From 02c38e5180a4071fcdd7a53d4b64e6e0a0296fc7 Mon Sep 17 00:00:00 2001 From: Quan Tian Date: Thu, 20 Sep 2018 11:30:05 +0800 Subject: [PATCH] Fix dns doc about inheriting DNS from nodes (#9214) Kubelet doesn't prepend the cluster DNS server to the nodes's DNS settings, neither for Pods with "ClusterFirst" dnsPolicy nor Pods with "default" dnsPolicy. Only pods with "default" dnsPolicy inherit DNS from nodes, without the cluster DNS server prepended. --- .../docs/tasks/administer-cluster/dns-custom-nameservers.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md b/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md index 76447cb678..b6eac169f1 100644 --- a/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md +++ b/content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md @@ -51,9 +51,9 @@ lookups (PTR records). ## Inheriting DNS from the node -When running a Pod, kubelet prepends the cluster DNS server and searches -paths to the node's DNS settings. If the node is able to resolve DNS names -specific to the larger environment, Pods should also be able to resolve. +If a Pod's `dnsPolicy` is set to "`default`", it inherits the name resolution +configuration from the node that the Pod runs on. The Pod's DNS resolution +should behave the same as the node. But see [Known issues](/docs/tasks/administer-cluster/dns-debugging-resolution/#known-issues). If you don't want this, or if you want a different DNS config for pods, you can