I think they care about their customers just about as much as they care about making money, and aside from GOG, the competition simply does not. It’s a pretty good demonstration to how capitalism has failed us, to be honest, because any of those competitors would have been able to compete if they hadn’t treated their customers like shit.
If you wanted to, you could post your /etc/resolv.conf and /etc/systemd/resolved.conf here. I don’t know if there might be a configuration directory option for systemd-resolved, so keep an eye out for a potential directory like /etc/systemd/resolved.d that might have the configs instead.
Uhm… interesting hyperbole during a time where America is literally facing down a fascist dictator.
Did you ever come back to this and figure it out? My curiosity is killing me :)
Oh, he absolutely will be. I hope to be there when we string them up on the capitol steps.
Let’s be perfectly honest, both parties have been selling us out to increasingly centralized corporations, who shipped our jobs overseas, peddled us ever shittier products, and killed off our local cultures and economies in favor of Walmart, Kroger, and Amazon.
But these are fascists now, and I can’t think of anything my inner anarchist hates more than fascists. But we should probably stop calling them nazis, they’re certainly supported by nazis, kkk, and others. But this is MAGA America, make no mistake. We need to wait for them to hurt enough people for the sentiment to turn against them, and then take it back at all costs.
It’s not too late. Only a matter of time before we normalize putting bullets in nazi brains, once again.
Agreed, though I don’t think they disabled systemd-resolved, because it still works using 127.0.0.53 when they’re connected to the VPN. So the daemon must be running, unless Mullvad itself has a DNS forwarder using the same loopback. I suspect they either hard coded some upstream DNS server for Mullvad, because Mullvad might not have supported systemd-resolved yet. Or maybe they set a permission on the configs, and something changed with the user context of Mullvad processes.
Interesting that it works when the VPN is connected, though. I also believe that systemd-resolved is installed on just about any system using systemd, but often isn’t enabled, without problem. Enabling it would generally involve a resolv.conf symlink and a config, so maybe that config was hijacked by Mullvad (or OP configuring Mullvad), and there’s no upstream DNS server available when the VPN isn’t connected.
I missed that it’s Linux Mint in the original post, and it looks like Mint has started using systemd-resolved. The Arch wiki might be useful to OP on how things are configured:
Ok, so something setup 127.0.0.53 as your DNS server, and isn’t removing it correctly. I think it’s safe to say it’s Mullvad, since it works using that DNS server IP when connected. Is that IP in your resolv.conf, or is resolv.conf maybe a stub, and you’re using systemd-resolved?
Ok, so does the VPN bring it’s own DNS? Some VPNs do, so it may explain why everything suddenly works fine when you connect.
When not connected to VPN, are you able to dig or nslookup internet names? Local names? A server timeout will be very different from an nxdomain or an empty SOA, in the response.
Are you able to telnet to a public web server on TCP/443?
One thought I’m having is, maybe at some point you set a static IP on your wifi interface, but screwed up the subnetting.
Have you ever messed with network manager or systemd-resolved internal settings, maybe trying to setup multicast DNS or caching?
Well, they probably want a leaner version for lower end phones anyway, along the lines of the Go versions of many of their apps. Luckily I won’t have to worry about this shit running Graphene, with no intention of running an LLM, so 8GB would be fine if I had any need to move on from my Pixel 8 prematurely.
Hey, maybe it’ll cause some fairly quick, large discounts. My Pixel 5 backup with a rather shattered screen could use a replacement.