extranuc:~# dig vaultwarden-service.default.svc.cluster.local
;; communications error to 10.43.0.10#53: timed out
;; communications error to 10.43.0.10#53: timed out

^ This was in my node extranuc:

NAME          STATUS   ROLES                  AGE   VERSION
extranuc      Ready    <none>                 3d    v1.32.3+k3s1
raspberrypi   Ready    control-plane,master   13d   v1.32.4+k3s1

I used netshoot for this, why am I getting time out issues?

kube-system       kube-dns                      ClusterIP      10.43.0.10      <none>                        53/UDP,53/TCP,9153/TCP       13d

io timeouts are only a issue on extranuc, also, it is using my hosts resolv.conf, and since previously it was using wrong ips for internal dns services, I added the kube-dns ip directly, for some reason, that isnt how its accessed, how to fix this? I have no network policies, and there is a firewall protecting port 53 from external access on extranuc, but I dont see how that would affect the issue