Error with pod hostname query

[bowei]

Query for the <pod-hostname>.<ns>.pods.cluster.local is not returning the A record for the pod

/ # dig customer-deployment-onuwixzygi4tkn3fgztgeylfgnrdm-62180010musmy.staging.pod.cluster.local.

kube-dns logs

I0316 16:18:30.889074       1 logs.go:41] skydns: error from backend: Invalid IP Address customer.deployment.onuwixzygi4tkn3fgztgeylfgnrdm.62180010musmy

[thockin]

Unless I misunderstand, we don't support that query, on purpose. We don't want DNS to have to watch all pods.

[exarkun]

https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ led me to believe this would work. However, a more careful re-reading now suggests that I probably combined information from a few different section - like the "Pods / A Records" section and the "A Records and hostname based on Pod’s hostname and subdomain fields" section - and invented the idea that this style hostname would work when the document doesn't appear to actually say this.

[bowei]

yeah -- brain fart on my part -- we should fix the documentation however, I don't think it's very clear

[seh]

If I understand the documentation correctly, so long as a headless Service named with the subdomain exists in the same namespace as the pods, kube-dns should publish A records for the pods. I find that this works only if the Service defines at least one port, even though the documentation says, "Actually, no port is needed."

Is the documentation wrong here, and a port should be required, or is this a defect in the implementation?

[thockin]

I think it should work without ports. File a new bug please, with a simple repro?

…

On Tue, Oct 24, 2017 at 10:13 AM, Steven E. Harris ***@***.*** > wrote: If I understand the documentation correctly, so long as a headless *Service* named with the subdomain exists in the same namespace as the pods, *kube-dns* should publish A records for the pods. I find that this works only if the *Service* defines *at least one port*, even though the documentation says <https://github.com/kubernetes/website/blame/master/docs/concepts/services-networking/dns-pod-service.md#L109>, "Actually, no port is needed." Is the documentation wrong here, and a port should be required, or is this a defect in the implementation? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#70 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFVgVH4xyrbQdyTt1tYOOoKmxHLbMdvxks5svhqigaJpZM4Mfr55> .

[seh]

@thockin, please see #174.