From 8df3312cdcb8d1213ea85f3e1a0d11b0b7c89853 Mon Sep 17 00:00:00 2001 From: Andrew Chen Date: Tue, 27 Jun 2017 09:33:50 -0700 Subject: [PATCH] Patch PR #4063 --- docs/tasks/administer-cluster/dns-custom-nameservers.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/tasks/administer-cluster/dns-custom-nameservers.md b/docs/tasks/administer-cluster/dns-custom-nameservers.md index dbdf56fb99..e6d925f556 100644 --- a/docs/tasks/administer-cluster/dns-custom-nameservers.md +++ b/docs/tasks/administer-cluster/dns-custom-nameservers.md @@ -55,8 +55,7 @@ data: [“8.8.8.8”, “8.8.4.4”] ``` -The diagram below shows the flow of DNS queries specified in the configuration -above. With the dnsPolicy set to “ClusterFirst”, a DNS query is first sent to +With the dnsPolicy set to “ClusterFirst”, a DNS query is first sent to the DNS caching layer in kube-dns. From there, the suffix of the request is examined and then forwarded to the appropriate DNS. In this case, names with the cluster suffix (e.g. “.cluster.local”) are sent to kube-dns. Names with the