Fedora 33 name resolution fails
Last Updated on December 9, 2023 by David Both
I just installed Fedora 33 today, the first day it became available. One of the major changes, a switch from the ancient nss resolver to systemd-resolved has already caused me a significant amount of trouble and borked my entire network. Get the whole story and the circumvention.
More Stories
Fedora rescue mode fails
Have you ever noticed the bottom line on the GRUB bootloader menu? Well, you won't unless you're looking for it...
A short review of Fedora 41
Fedora 41 was released on October 29, and I installed it on my primary workstation within a few minutes after...
VirtualBox failures
I just tried to update VirtualBox and encountered some strange problems. It started when a student of mine tried to...
How I create Linux device files — and why
First, what the heck is a Linux device file -- and why should I care? Linux handles almost everything as...
How to untangle the systemd-resolved DNS mess
The change from the venerable nsswitch and NetworkManager to systemd-resolved has damaged and slowed name services. The result of this resolver change was apparent in a number of symptoms. Inability to find the addresses of most remote servers resulting in timeouts was the most noticeable. When the connections were made, They were very slow to respond. I didn’t really understand how much slower until after I fixed the problem.
A little Vim trick I learned today
I learned a neat new trick today that greatly improves my work with Vim when I'm editing code. I like...