title: Cafe wifi DNS hijacking and kops validate cluster
body: <p>I have created kops cluster many times before (on office internet connection) and have not changed my cluster config.<br>
  Only thing i am doing different now is trying to work from a cafe wifi.</p>
  
  <p><code>kops validate cluster</code> gives the error:<br>
  <code>Unable to connect to the server: dial tcp: lookup api-REDACTED.us-east-1.elb.amazonaws.com on 8.8.8.8:53: no such host</code></p>
  
  <p>I have found this <a href="https://github.com/kubernetes/kops/issues/1386" rel="nofollow noreferrer">discussion on kops github</a> which seems to suggest DNS just takes time to propagate, maybe 15 minutes or more.<br>
  But my experience (working in office internet environment) suggests that kops and aws does not take so long to register and create the cluster.    </p>
  
  <p>I am not too familiar with DNS, I am thinking it might be due to cafe wifi having a different DNS?<br>
  I have read that   </p>
  
  <blockquote>
    <p>Some DNS providers practice DNS hijacking while processing queries, redirecting web browsers to an advertisement site operated by the provider when a nonexistent domain name is queried.<br>
    From <a href="https://en.wikipedia.org/wiki/Google_Public_DNS" rel="nofollow noreferrer">https://en.wikipedia.org/wiki/Google_Public_DNS</a>  </p>
  </blockquote>
  
  <p>Which seems to make sense since this Starbucks periodically throws me out of the wifi connection and <em>serves me some latte ads</em>.  </p>
  
  <p>What is the workaround for this?  Can I make my wifi connection not DNS-hijacked in a cafe wifi setting?  </p>