<p>i have a lab environment with a bind server. The server manages the domain "lab.local" DNS Dynamic Update are configured. The lab client (windows and linux) are using the DNS server.</p>

<p>Now i would like do use a kubernetes cluster in our lab. Can i use the bind server with the zone "lab.local" with kubernetes? </p>

<p>For example: i would like to create a nginx pod and access it from my client over nginx.lab.local. I have looked at <a href="https://github.com/kubernetes-incubator/external-dns" rel="nofollow noreferrer">https://github.com/kubernetes-incubator/external-dns</a> but i didn't find any Information how to use it with bind.</p>

DanMar
<p>Once the nginx Pod has been created, it will have a internal IP by default, not addressable from your lab network (only other pods can access it).</p>

<p>To access it from the lab network, expose it as a Service with type as <a href="https://kubernetes.io/docs/concepts/services-networking/service/#nodeport" rel="nofollow noreferrer">NodePort</a> and then it will have a external routable IP address. Then add an entry in the bind server to that external routable IP address for everyone to access using the URL.</p>

<p>There are other and better ways also of exposing a Service by using a <a href="https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer" rel="nofollow noreferrer">Load Balancer</a> or an <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/" rel="nofollow noreferrer">Ingress</a>. For those who are new or getting started with K8S, exposing the Pod using NodePort is the easiest to see some quick results.</p>
