<p>I've created a Kubernetes cluster using CoreOS on AWS and I'm having trouble communicating with nodes from the master.</p>

<p>For example, operations like <code>kubectl exec</code> or <code>kubectl logs</code> fail an error similar to the following:</p>

<pre><code>Error from server: dial tcp: lookup ip-XXX-X-XXX-XXX.eu-west-1.compute.internal: no such host
</code></pre>

<p>I've found some issues on Github that describe the problem so I know the team knows about this bug, but I would like to ask here if its possible to use some workaround until it gets addressed somehow.</p>

<p>One workaround mentioned was to use the <code>--hostname-override</code> flag but as I'm on AWS, this flag is ignored (see <a href="https://github.com/kubernetes/kubernetes/issues/22984" rel="noreferrer">#22984</a>)</p>

<p>Related issues on GitHub: <a href="https://github.com/kubernetes/kubernetes/issues/22770" rel="noreferrer">#22770</a> <a href="https://github.com/kubernetes/kubernetes/issues/22063" rel="noreferrer">#22063</a>.</p>

<p>Have you made sure you're using the right context?</p>

<pre><code>kubectl config use-context my-cluster-name 
</code></pre>
