<p>We have deployed a K8S cluster using ACS engine in an Azure public cloud.
We are able to create deployments and services but when we enter a pod using "<strong>kubectl exec -ti (pod name) (command)</strong>" we are receiving the below error,</p>

<blockquote>
  <p><strong>Error from server: error dialing backend: dial tcp: lookup (node hostname) on 168.63.129.16:53: no such host</strong></p>
</blockquote>

<p>I looked all over the internet and performed all I could to fix this issue but no luck so far.
The OS is Ubuntu and 168.63.129.16 is a public IP from Azure used for DNS.(refer below link)</p>

<blockquote>
  <p><a href="https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is-the-ip-address-168-63-129-16/" rel="noreferrer">https://blogs.msdn.microsoft.com/mast/2015/05/18/what-is-the-ip-address-168-63-129-16/</a></p>
</blockquote>

<p>I've already added host entries to <strong>/etc/hosts</strong> and entries into <strong>resolv.conf</strong> of the master/node server and nslookup resolves the same. I've also tested by adding <strong>--resolv-conf</strong> flag to the kubelet but still it fails. I'm hoping that someone from this community can help us fix this issue.</p>

<p>Verify the node on which your pod is running can be resolved and reached from inside the API server container. If you added entries to <code>/etc/resolv.conf</code> on the master node verify they are visible in the APIserver container, if they are not, restarting the API server pod might be helpful </p>
