kind-air-74358
05/08/2023, 9:03 AMnslookup
fails with error ;; connection timed out; no servers could be reached
When running nslookup <http://google.com|google.com> 10.36.0.116
from multitool running on the control-plane-01 host I get a valid response, running nslookup <http://google.com|google.com> 10.36.1.185
it fails with the connection timed out error. Same behaviour when running this in the multitool pod on the worker-01 host.
My guess is that our external firewall is blocking some connections, but I can’t find out which ports I should whitelist.
I verified that all the ports mentioned on https://docs.rke2.io/install/requirements#inbound-network-rules (Kubernets specific ones and the Cilium ones) are open and allowed port 53 for TCP and UDP traffic between all the cluster hosts.