Good morning. I seem to be having some issues with...
# k3s
s
Good morning. I seem to be having some issues with DNS and I'm not sure the exact cause
Copy code
# kubectl -n longhorn-system exec -it longhorn-manager-5p89q -- nslookup longhorn-backend
Defaulted container "longhorn-manager" out of: longhorn-manager, pre-pull-share-manager-image
;; communications error to 10.43.0.10#53: timed out
;; communications error to 10.43.0.10#53: timed out
^C
command terminated with exit code 1

# kubectl -n longhorn-system exec -it longhorn-manager-wf997 -- nslookup longhorn-backend
Defaulted container "longhorn-manager" out of: longhorn-manager, pre-pull-share-manager-image
;; Got recursion not available from 10.43.0.10
Server:		10.43.0.10
Address:	10.43.0.10#53

Name:	longhorn-backend.longhorn-system.svc.cluster.local
Address: 10.43.107.35
;; Got recursion not available from 10.43.0.10
Basically some nodes are able to reach the DNS service while others aren't. Any idea how to solve this?
Ah it was multicloud so needed external IP. Tailscale fixed the issue somewhat - a few nodes went down after turning on tailscale though - not sure the problem. will keep debugging
It was working for a bit and it's down again. Can't seem to figure out why DNS just isn't reliable
Ah every time I restart k3s the tailscale/headscale routes are reset