It's not that simple. The biggest issue is that Apple Silicon uses 16K memory page sizes instead of the 4K pages used by pretty much every other architecture out there. This means you'd need a kernel patched for 16K pages - but that would also cause an issue with drivers and other apps designed with 4K pages in mind. So there's a lot of work done in that area to get both the kernel and apps working. Even then, some apps may never work, and so you'd have to resort to using hacks like microVMs to run a 4K kernel and then run the app on top of it, but that introduces it's own set of issues of course.
Then there's the issue of hardware components - of course Apple hasn't open-sourced any of their firmware/drivers, so most of the Asahi drivers were developed by reverse engineering. The GPU was the biggest piece of work, the reverse engineering done to get it to a workable state by the Asahi team was nothing short of genius. In fact the current state of the OpenGL driver is so good that it's far, far more compliant to the spec compared to macOS itself - macOS only supports OpenGL upto 4.1 and is not certified either (and technically no longer supported by Apple), whereas Asahi supports up till 4.6 - and it's still being improved. See: https://arstechnica.com/gadgets/2024/02/asahi-linux-projects-opengl-support-on-apple-silicon-officially-surpasses-apples/
Similarly, a lot of wizardry was done to get the sound going, and not only did they get it going - they even improved the DSP so it sounds even better than macOS! (Scroll down to the speakers section here: https://asahilinux.org/2024/01/fedora-asahi-new/).
But in spite of all that, there's still a lot of work to be done, such as getting Thunderbolt and DisplayPort going, as well as improving compatibility with x86 apps (using krun and FEX) and more GPU improvements etc and support for the M3 and newer chips.. Even then, Asahi is already in a usable daily-driver state for many users, and it's improving at a rapid pace.
So long story short, the Asahi team had to do a ton of work to get it all going on a complex, closed piece of hardware like Apple Silicon - and it's genius levels of work, the level of which I can barely comprehend - and isn't something any random distro can pull off.
Sounds like an issue with your WiFi adapter/driver. You can verify this by creating a mobile hotspot on your phone and connecting your PC to it and see if you get the same issue, if you do then it proves it's got nothing to do with your router.
Another thing you can check is your journalctl logs - run
journalctl -fbefore launching the game, then run the game and quit it when you run into the DNS issue, and check the logs at the time the issue occurred. If there's indeed a hardware/driver issue, the errors should show up in the logs.If it's a driver issue, there may not be much you can do about it besides reporting the bug and implementing some sort of workaround (eg using a VPN). Of course, depending on the error, there may be a fix you can apply, like turning of aspm for your chip. A better option would be to replace the WiFi chip/adapter you're using and get something that's better supported under Linux, like something with an Intel or Atheros chip. But check journalctl first and see how it goes from there.