From 2ebcf10831a571a6a4f4abb3cbed37e6feb554a9 Mon Sep 17 00:00:00 2001 From: Namhoon Lee Date: Wed, 16 Jan 2019 10:45:07 +0900 Subject: [PATCH] Update dns-pod-service.md (#10788) Fix pod's DNS address --- .../en/docs/concepts/services-networking/dns-pod-service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/dns-pod-service.md b/content/en/docs/concepts/services-networking/dns-pod-service.md index 5c519d479a..da5162073b 100644 --- a/content/en/docs/concepts/services-networking/dns-pod-service.md +++ b/content/en/docs/concepts/services-networking/dns-pod-service.md @@ -84,7 +84,7 @@ the hostname of the pod. For example, given a Pod with `hostname` set to The Pod spec also has an optional `subdomain` field which can be used to specify its subdomain. For example, a Pod with `hostname` set to "`foo`", and `subdomain` set to "`bar`", in namespace "`my-namespace`", will have the fully qualified -domain name (FQDN) "`foo.bar.my-namespace.svc.cluster.local`". +domain name (FQDN) "`foo.bar.my-namespace.pod.cluster.local`". Example: @@ -141,7 +141,7 @@ record for the Pod's fully qualified hostname. For example, given a Pod with the hostname set to "`busybox-1`" and the subdomain set to "`default-subdomain`", and a headless Service named "`default-subdomain`" in the same namespace, the pod will see its own FQDN as -"`busybox-1.default-subdomain.my-namespace.svc.cluster.local`". DNS serves an +"`busybox-1.default-subdomain.my-namespace.pod.cluster.local`". DNS serves an A record at that name, pointing to the Pod's IP. Both pods "`busybox1`" and "`busybox2`" can have their distinct A records.