Permalink
Browse files

Correct minor error (#9690)

Technically speaking SRV targets are address record names, not CNAMEs.  In fact, the SRV RFC states that SRV targets must point to an address record name, and cannot be an alias (e.g. CNAME).
  • Loading branch information...
chrisohaver authored and k8s-ci-robot committed Jul 31, 2018
1 parent 80e659c commit 0f9262b8eb5c4378fa305d2d2ee2f2b2dc3b4881
Showing with 2 additions and 2 deletions.
  1. +2 −2 content/en/docs/concepts/services-networking/dns-pod-service.md
@@ -56,10 +56,10 @@ SRV Records are created for named ports that are part of normal or [Headless
Services](/docs/concepts/services-networking/service/#headless-services).
For each named port, the SRV record would have the form
`_my-port-name._my-port-protocol.my-svc.my-namespace.svc.cluster.local`.
For a regular service, this resolves to the port number and the CNAME:
For a regular service, this resolves to the port number and the domain name:
`my-svc.my-namespace.svc.cluster.local`.
For a headless service, this resolves to multiple answers, one for each pod
that is backing the service, and contains the port number and a CNAME of the pod
that is backing the service, and contains the port number and the domain name of the pod
of the form `auto-generated-name.my-svc.my-namespace.svc.cluster.local`.
## Pods

0 comments on commit 0f9262b

Please sign in to comment.