This message was deleted.

K3D_FIX_DNS

is still a thing. Does that not work for you?

It does, I just discovered this issue yesterday and it seemed pretty old, and new release just happened, so I decided to ask. And yes, it looks like working for me, thank you very much! Hope it will be available in some of next releases. Just to clarify, I have win10, WSL2 (ubuntu) and running k3d 5.6.0 there. I am in corporate network (haven't tested VPN "working from home" yet), and now resolv.conf in pod contains not

127.0.0.11

but

10.43.0.10

which seems to do the trick (DNS on WSL is

192.168...

. Both intranet and internet names are resolved correctly.

Great! Yeah, I'd need to default that do enabled in some future release.