Cannot access DNS server from k0s pods that lives in WSL

All about k0s
#1

Hi,

I have two k0s installations, and both are in a WSL environment. The one on my personal computer works fine, and can access public DNS servers. However, the one on my company computer cannot access any DNS server, not even a dnsmasq service on the same machine.

While testing the k0s on my company computer, I updated coredns to forward queries to my local dnsmasq server. I can see the queries from the coredns pod when it initializes, but the coredns log shows it cannot get responses from the DNS server.

My company computer may have some firewall rules blocking the DNS queries. If I could identify the rule, I could work with our IT security to resolve this. It does not make sense to block DNS queries from the k0s cluster.

Thanks.

#2

Sorry, I am not entirely sure it has anything to do with company IT security.

Here are the observations:

  1. My WSL cannot access any public DNS, like 1.1.1.1.
  2. My WSL can access a dnsmasq server on my Windows host.
  3. Pods in my k0s cannot access any DNS, not even the dnsmasq on my Windows host.

Most strangely, in a pod with DNS utilities, if I try to query against my dnsmasq server, I can see the query logs in my dnsmasq server, but the dns utility in the pod still responds timeout.

#3

That sounds like the networking between the WSL and Windows is somehow broken, i.e. the responses are not properly routed back or something.

#4

Hello,
were you able to resolve it and find root cause?