this is weird though
Debugging happened in private, it seemed to be a Mullvad issue 
Was there a technical solution beyond “pick a different server”? The troubleshooting steps might be helpful for other who has this issue.
Great job @solene!
@solene had me check the output of systemd-resolve and the output of /etc/resolv.conf to check the DNS. I also restarted systemctl restart systemd-resolved.
In the end, I made a new fedora41 appvm @Cracked_Tessaract
Copied a completely different wireguard .conf over and ran nmcli connection import type wireguard file vpn.conf per solenes guide.
curl https://am.i.mullvad.net/connected returns successful connection. there appear to be 2 servers in my region affected with DNS issues. never had issues with mullvad before…
2 Likes
I was able to make my wireguard vm disposable like sys-net or at least I think I did, is that something someone else has already done or should I try and post about how I did it? If I should post about it, should it just be a reply to this post or a new one all together?
This kind of operation should be straightforward or common enough that it should be documented separately if it’s not already in the documentation.
But if you really want to, you can edit the first post and add an extra section at the end about making the VPN from a disposable
Got it, I’ll write up how I did it soon in its own post.