Add-on dns

thanks! I will update this page

Your question helped me resolve my own similar issue.

I havenā€™t tried multiple microk8s nodes yet, but I did make the mistake of using one private and one public DNS server on my single node clusterā€™s DNS settings. This created hit-and-miss lookups on my pods, particularly on private resources (which I should have guessed).

Iā€™m running in WSL2, and I got my DNS server from:

nslookup foo | grep Server
Server:         192.168.176.1

This is what got me into trouble:

# don't do this
microk8s enable dns:192.168.176.1,1.1.1.1

Using just the private one granted me access to public and private, as you noted:

# this worked in my case
microk8s enable dns:192.168.176.1

Not sure if this will help your use case, but I hope it helps somebody in similar circumstances.


Host: Ubuntu 22.04 running in WSL2
Channel: 1.25-eksd/stable

1 Like

Hello, now in 2024, has anyone found solution to this? I tried to set 2 replicas of coredns for my two-nodes cluster, add hosts to /etc/hosts ā€¦ but none of them worked.

1 Like

Hi, can you give us more details about the setup of your nodes, your configuration and what didnā€™t work as you expected?