From a9b1cdb4e98dafbe67cb1b34996f2f21765a3c36 Mon Sep 17 00:00:00 2001
From: Denis Salamanca <33235720+dsalamancaMS@users.noreply.github.com>
Date: Fri, 20 Jul 2018 17:08:33 -0600
Subject: [PATCH] Updated dns-pod-service.md (#9552)

* Updated dns-pod-service.md

Added a note on A records creation

* Updated dns-pod-service.md

Added Hugo  {{ note }} shortcode

* Update dns-pod-service.md

Changed wording

* tighten up the wording
---
 .../en/docs/concepts/services-networking/dns-pod-service.md   | 4 ++++
 1 file changed, 4 insertions(+)

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 1db0cc6f05..8baa30b006 100644
--- a/content/en/docs/concepts/services-networking/dns-pod-service.md
+++ b/content/en/docs/concepts/services-networking/dns-pod-service.md
@@ -148,6 +148,10 @@ A record at that name, pointing to the Pod's IP. Both pods "`busybox1`" and
 The Endpoints object can specify the `hostname` for any endpoint addresses,
 along with its IP.
 
+{{< note >}}
+**Note:** Because A records are not created for Pod names, `hostname` is required for the Pod's A record to be created. A Pod with no `hostname` but with `subdomain` only will only create the A record for the headless service (`default-subdomain.my-namespace.svc.cluster.local`), pointing to the Pod's IP address.
+{{< /note >}}
+
 ### Pod's DNS Policy
 
 DNS policies can be set on a per-pod basis. Currently Kubernetes supports the