[lima] K3s split-DNS (again)

I just gave 0.6.0 a shot and my split-DNS from the host is not working in the container (see https://github.com/rancher-sandbox/rancher-desktop/issues/702).

I’ve been using Lima 0.7.1 just fine and it worked well (after the https://github.com/lima-vm/lima/pull/281). It doesn’t when installed with RD. I did a full reset and manually deleted lima.yaml just to make sure.

I can confirm that the DNS resolution works well in the VM but not in the containers. CoreDNS is not able to resolve private addresses. I checked coredns config map and it seems fine (all-defaults). If I do dig +short @192.168.5.33 private-host (an IP from /etc/resolve.conf in the VM) in the container - it gives nothing, though it works in the VM itself.

[jandubois]

I originally tried PREROUTING and POSTROUTING rules, but couldn’t get them to work: https://github.com/lima-vm/lima/pull/281#issuecomment-931940795

But that was when I was still trying to redirect to 127.0.53.53. It doesn’t work because localhost traffic isn’t processing pre- and post-routing chains, which is why I switched to the output chain. But since we are now redirecting to an external address, this limitation no longer applies.

I am afraid it might break something […] - thoughts?

I need to think about this for a while; will get back to you later

[dee-kryvenko]

Ok I believe I’ve figured SRV out… adding now.