2 ms·
The upgrade to Fedora 33 killed my laptop's internet, as well, due to the switch over to systemd-resolved. I figured it had to be DNS related, because some of m
by AdmiralAsshat 6y ago
The upgrade to Fedora 33 killed my laptop's internet, as well, due to the switch over to systemd-resolved. I figured it had to be DNS related, because some of my programs were able to connect to the internet, while anything at the OS-level was failing. While troubleshooting, I was able to at least restore Firefox to a working state by enabling DNS-over-HTTPS, and that confirmed my theory, since it was essentially offloading DNS lookup from the OS to a third-party service.
Fixing it required issuing this not-at-all intuitive command on the command-line:
sudo nmcli connection modify id CON_NAME \
ipv4.ignore-auto-dns yes ipv6.ignore-auto-dns yes
Fuck if I know what it's doing, and that fix was only applied to my individual home WiFi network, so, for all I know it will still be broken the next time I'm at a coffee shop.
- marcosdumay 6y ago> Fuck if I know what it's doing It's the Network Manager command line tool (nice to know its name, that's why I could never find it). The option you are setting has this description: "Do not use DNS Resolver from DHCP". I didn't find a GUI switch on my computer with that meaning.
- AdmiralAsshat 6y agoThanks, I think I did eventually figure that out via googling, but the documentation then said it would use "hard-coded public DNS servers", which didn't sound great. And yeah, I think my bigger irk is that this seems to contradict the network settings in my DE's GUI, where I had explicitly tried setting the DNS lookup servers to 1.1.1.1 instead of using DHCP.