Stanislav Plakhin

The solution is to bind dnsmasq to different port, smth like 5353. Then use smth like YogaDNS and configure it to resolve *.test using 127.0.0.1:5353 (I guess dnsmasq should be...

I've already posted the working solution for wildcard domains. Another option is just to set up your windows to use 127.0.0.1 as DNS server, but then you need WSL and...

You should have access to services running inside WSL on 127.0.0.1:port by TCP and UDP. Like you have an access to nginx. The trick is to bind dnsmasq to different...

Did you try different port, not 53? Do you access WSL by 127.0.0.1? Did you uninstall acrylic and/or other software which can impact? Did you try to disable windows firewall?

I've looked at microsoft/WSL#4592. Information there is either quite outdated (there was changes to WSL2 before official release of 2004 update) or irrelevant to proposed solution.

As a workaround https://github.com/TechnitiumSoftware/DnsServer/ can be used, You can install on windows host and create `.test` (or whatever) zone there, then create `*` record of `A` type and IPv4 Address...

I was using it with WSL2 without any problems. I wasn't using dnsmasq inside WSL2 and my antivirus is default windows defender. Later I switched back to manual host addition...

YogaDNS authors promised to add a rule to resolve any wildcard domain to specific IP (or just localhost) in the next release. But hosts is not the main problem. The...

@stancl, any approximate release date? at least for the beta

> You already said you would look at it for v4 on issue #250 itself, but for overview purposes: having a solution for slow tests documented and in the boilerplate....