kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Apply suggestions from code review 

Co-authored-by: Tim Bannister <tim@scalefactory.com>
pull/49532/head
David Xia 2025-01-28 15:48:01 -05:00
parent 95913f9dae
commit c6fb12d440
No known key found for this signature in database
GPG Key ID: 5F38B0A1B60734DF
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -107,10 +107,9 @@ and the domain name for your cluster is `cluster.local`, then the Pod has a DNS
`172-17-0-3.default.pod.cluster.local`.
If you're using [CoreDNS], Pods exposed by a Service will also have the following
DNS resolution available:
Some cluster DNS mechanisms, like [CoreDNS], also provide `A` records for:
`pod-ipv4-address.service-name.my-namespace.svc.cluster-domain.example`.
<tt><em>pod-ipv4-address</em>.<em>service-name</em>.<em>my-namespace</em>.svc.<em>cluster-domain.example</em>.</tt>
### Pod's hostname and subdomain fields
@ -365,4 +364,4 @@ this problem.
For guidance on administering DNS configurations, check
[Configure DNS Service](/docs/tasks/administer-cluster/dns-custom-nameservers/)
[CoreDNS]: /docs/tasks/administer-cluster/coredns/
[CoreDNS]: https://coredns.io/