title: dns error, no such host on google-container-engine
body: <p>we're trying to get Let's Encrypt up and running inside kubernetes with <a href="https://github.com/kelseyhightower/kube-cert-manager" rel="nofollow">kube-cert-manager</a>.</p>
  
  <p>When running <code>kube-cert-manager</code><a href="https://github.com/kelseyhightower/kube-cert-manager/blob/master/dns.go#L103" rel="nofollow">this function</a> is called to monitor the dns propagation which checks if the ACME challenge is found inside the dns TXT record.<br>
  When this gets called this error gets logged.</p>
  
  <pre><code> 2016/09/05 12:52:47 monitorDNSProgragation error: lookup foo.bar.de on 10.71.240.10:53: no such host
  </code></pre>
  
  <p><code>10.71.240.10</code> is the DNS server used everywhere inside our kubernetes cluster. I can resolve <code>foo.bar.de</code> in every container (pod) inside the cluster using <code>dig</code>. This is also possible in the <code>kube-cert-manger</code> container.<br>
  It's just not possible with the <code>kube-cert-manager</code> binary.</p>
  
  <p><code>kube-cert-manager</code> uses <a href="https://github.com/miekg/dns" rel="nofollow">github.com/miekg/dns</a>. I've replaced the function linked above with stdlib <code>net.LookupTXT(c.domain)</code> which returns the same error.</p>
  
  <p>Is this some Go bug?<br>
  Some known configuration error in google-container-engine?</p>
  
  <p>If you need more information just ask. </p>
  
  <p>Thanks.</p>