Skip to content

Commit 6e0c04e

Browse files
authored
Merge pull request #49532 from davidxia/patch-5
fix: clarify that certain Pod A records are only available with CoreDNS
2 parents fea8d97 + c6fb12d commit 6e0c04e

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

content/en/docs/concepts/services-networking/dns-pod-service.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,9 +107,9 @@ and the domain name for your cluster is `cluster.local`, then the Pod has a DNS
107107

108108
`172-17-0-3.default.pod.cluster.local`.
109109

110-
Any Pods exposed by a Service have the following DNS resolution available:
110+
Some cluster DNS mechanisms, like [CoreDNS], also provide `A` records for:
111111

112-
`pod-ipv4-address.service-name.my-namespace.svc.cluster-domain.example`.
112+
<tt><em>pod-ipv4-address</em>.<em>service-name</em>.<em>my-namespace</em>.svc.<em>cluster-domain.example</em>.</tt>
113113

114114
### Pod's hostname and subdomain fields
115115

@@ -363,3 +363,5 @@ this problem.
363363

364364
For guidance on administering DNS configurations, check
365365
[Configure DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers/)
366+
367+
[CoreDNS]: https://coredns.io/

0 commit comments

Comments
 (0)