Samuel Hilson

It's one of the know issues in WSL2. Acrylic Proxy causes issues https://github.com/microsoft/WSL/issues/4364. Also, none of the host file hacks you can find out there are going to allow wildcard...

@Himakar-PV I am not sure what this problem has to do with Valet WSL. Maybe you are wanting to create issue on the WSL repo?

I don't know if dnsmasq will work yet. I will have to check into it. https://github.com/microsoft/WSL/issues/4592

Acrylic always binds to port 53, the issues is that now in wsl2 dnsmasq is also binding port 53 and that is getting bound on the host system. You can...

My system finally upgraded to windows 2004. I will try to look into getting this working but Microsoft has not really given any indications that they find it worthwhile to...

Host file hacks do not support wildcard domains and will never be capable of providing the coverage of a dns proxy. If your project only uses a simple single domain...

You are using virtual box, wsl has a different network stack and communication between windows and dnsmasq is broken as I have pointed out before: https://github.com/microsoft/WSL/issues/4592

Should is the important word there. But currently it does not work for dns like it does for other services. Which is the point of the issue I linked.

Did you look at at the issue I posted and everything everyone has tried... There is a possible work around near the end but it is unreliable and requires some...

That's not very doable when you have hundreds of projects or a need for wildcard domains. The host file is well know to most developers but does not fulfill their...