<p>is it possible to do a reverse DNS lookup from one pod to another in the same namespace on Kuberenetes?
Setup: Kubernetes 1.5, kube-dns 1.9</p>

<p>When I exec a pod with nslookup I don't get a hostname but only a nslookup timeout like:</p>

<pre><code>$ time kubectl exec mypod -- nslookup 172\.18\.14\.13

nslookup: can't resolve '(null)': Name does not resolve Name:     
172.18.14.13 Address 1: 172.18.14.13
</code></pre>

<p>real    0m5.592s</p>

<p>mypod2 does have the internal IP 172.18.14.13. Both mypod and mypod2 have been deployed to the same namespace (default).</p>

<p>A nslookup from mypod to mypod works:</p>

<pre><code>$ time kubectl exec mypod -- nslookup 172\.18\.58\.13
nslookup: can't resolve '(null)': Name does not resolve

Name:      172.18.58.13
Address 1: 172.18.58.13 mypod

real    0m0.403s
</code></pre>

<p>Do I have to configured something special or isn't it possible by design?</p>

<p>The conclusion is that it's impossible by design.</p>

<p>General pod ip reverse lookup require a lot of work in kubedns and kubernetes, and this does not have many use cases. While headless services dns reverse lookup is supported after kubedns 1.11.</p>

<p>You can get more discussion about this in <a href="https://github.com/kubernetes/kubernetes/issues/33470" rel="nofollow noreferrer">issue#33470</a> and <a href="https://github.com/kubernetes/dns/pull/25" rel="nofollow noreferrer">PR#25</a></p>
