# Kubernetes Cluster on nodes with multiple NICs **URL:** \ **Category:** General Discussions\ **Created:** [September 11, 2018, 4:37pm UTC](https://discuss.kubernetes.io/t/kubernetes-cluster-on-nodes-with-multiple-nics/2720 "2018-09-11T16:37:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![russells](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/russells/32/1420_2.png) [@russells](https://discuss.kubernetes.io/u/russells)\ **Post date:** [September 11, 2018, 4:37pm UTC](https://discuss.kubernetes.io/t/kubernetes-cluster-on-nodes-with-multiple-nics/2720/1 "2018-09-11T16:37:41Z")
I have a 4 node Kubernetes cluster, 1 x controller and 3 x workers. The following shows how they are configured with the versions. ```auto NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME k8s-ctrl-1 Ready master 1h v1.11.2 192.168.191.100 Ubuntu 18.04.1 LTS 4.15.0-1021-aws docker://18.6.1 turtle-host-01 Ready 1h v1.11.2 192.168.191.53 Ubuntu 18.04.1 LTS 4.15.0-29-generic docker://18.6.1 turtle-host-02 Ready 1h v1.11.2 192.168.191.2 Ubuntu 18.04.1 LTS 4.15.0-34-generic docker://18.6.1 turtle-host-03 Ready 1h v1.11.2 192.168.191.3 Ubuntu 18.04.1 LTS 4.15.0-33-generic docker://18.6.1 ``` Each of the nodes has two network interfaces, for arguments sake `eth0` and `eth1`. `eth1` is the network that I want to the cluster to work on. I setup the controller using `kubeadm init` and passed `--api-advertise-address 192.168.191.100`. The worker nodes where then joined using this address. Finally on each node I modified the kubelet service to have `--node-ip` set so that the layout looks as above. The cluster appears to be working correctly and I can create pods, deployments etc. However the issue I have is that none of the pods are able to use the `kube-dns` service for DNS resolution. This is not a problem with resolution, rather that the machines cannot connect to the DNS service to perform the resolution. For example if I run a `busybox` container and access it to perform `nslookup` i get the following: ```auto / # nslookup www.google.co.uk nslookup: read: Connection refused nslookup: write to '10.96.0.10': Connection refused ``` I have a feeling that this is down to not using the default network and because of that I suspect some Iptables rules are not correct, that being said these are just guesses. I have tried both the Flannel overlay and now Weave net. The pod CIDR range is `10.32.0.0/16` and the service CIDR is as default. I have noticed that with Kubernetes 1.11 there are now pods called `coredns` rather than one `kube-dns`. I hope that this is a good place to ask this question. I am sure I am missing something small but vital so if anyone has any ideas that would be most welcome. ---
**Author:** ![russells](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/russells/32/1420_2.png) [@russells](https://discuss.kubernetes.io/u/russells)\ **Post date:** [September 11, 2018, 4:43pm UTC](https://discuss.kubernetes.io/t/kubernetes-cluster-on-nodes-with-multiple-nics/2720/2 "2018-09-11T16:43:33Z")
> [@russells](#): > > e I apologise for posting a technical question on here. I have now asked it on SO. ---
**Author:** ![castrojo](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/castrojo/32/8_2.png) [@castrojo](https://discuss.kubernetes.io/u/castrojo)\ **Post date:** [September 12, 2018, 3:05pm UTC](https://discuss.kubernetes.io/t/kubernetes-cluster-on-nodes-with-multiple-nics/2720/3 "2018-09-12T15:05:18Z")
Hey no worries! Can you post a link so we can close the loop, perhaps get some more eyes on your question? Thanks! ---
**Author:** ![mrbobbytables](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/mrbobbytables/32/7_2.png) [@mrbobbytables](https://discuss.kubernetes.io/u/mrbobbytables)\ **Post date:** [September 12, 2018, 4:23pm UTC](https://discuss.kubernetes.io/t/kubernetes-cluster-on-nodes-with-multiple-nics/2720/4 "2018-09-12T16:23:30Z")
It’s all good 🙂 Other folk do post technical questions on here as well. You may just wind up getting more eyes on it over there from a troubleshooting perspective. ---
**Author:** ![russells](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/russells/32/1420_2.png) [@russells](https://discuss.kubernetes.io/u/russells)\ **Post date:** [September 12, 2018, 7:20pm UTC](https://discuss.kubernetes.io/t/kubernetes-cluster-on-nodes-with-multiple-nics/2720/5 "2018-09-12T19:20:49Z")
As requested here is the link to my SO post - [https://stackoverflow.com/questions/52280629/how-does-dns-resolution-work-on-kubernetes-with-multiple-networks](https://stackoverflow.com/questions/52280629/how-does-dns-resolution-work-on-kubernetes-with-multiple-networks) Thanks for the replies :-).