<p>I'm using Kubernetes v1.0.6 on AWS that has been deployed using <code>kube-up.sh</code>.<br>
Cluster is using <code>kube-dns</code>.</p>

<pre><code>$ kubectl get svc kube-dns --namespace=kube-system
NAME       LABELS                                                                           SELECTOR           IP(S)       PORT(S)
kube-dns   k8s-app=kube-dns,kubernetes.io/cluster-service=true,kubernetes.io/name=KubeDNS   k8s-app=kube-dns   10.0.0.10   53/UDP
</code></pre>

<p>Which works fine.</p>

<pre><code>$ kubectl exec busybox -- nslookup kubernetes.default
Server:    10.0.0.10
Address 1: 10.0.0.10 ip-10-0-0-10.eu-west-1.compute.internal

Name:      kubernetes.default
Address 1: 10.0.0.1 ip-10-0-0-1.eu-west-1.compute.internal
</code></pre>

<p>This is the <code>resolv.conf</code> of a pod.</p>

<pre><code>$ kubectl exec busybox -- cat /etc/resolv.conf
nameserver 10.0.0.10
nameserver 172.20.0.2
search default.svc.cluster.local svc.cluster.local cluster.local eu-west-1.compute.internal
</code></pre>

<p>Is it possible to have the containers use an additional nameserver?</p>

<p>I have a secondary DNS based service discovery Oon let's say 192.168.0.1) that I would like my kubernetes containers to be able to use for dns resolution.</p>

<p>ps. A kubernetes 1.1 solution would also be acceptable :)</p>

<p>Thank you very much in advance,
George</p>

<p>The <a href="https://github.com/kubernetes/kubernetes/blob/b9cfab87e33ea649bdd13a1bd243c502d76e5d22/cluster/addons/dns/README.md#inheriting-dns-from-the-node" rel="nofollow">DNS addon README</a> has some details on this. Basically, the pod will inherit the <code>resolv.conf</code> setting of the node it is running on, so you could add your extra DNS server to the nodes' <code>/etc/resolv.conf</code>. The <code>kubelet</code> also takes a <a href="https://github.com/kubernetes/kubernetes/blob/69a8dc64c72b6268ebeb8cd03493aa219643a79d/cmd/kubelet/app/server.go#L284" rel="nofollow"><code>--resolv-conf</code> argument</a> that may provide a more explicit way for you to inject the extra DNS server. I don't see that flag documented anywhere yet, however.</p>
