Fedora name resolution fails
Last Updated on January 25, 2025 by David Both
Image by: Opensource.com: CC-by-SA 4.0
I installed Fedora 33 on October 27, 2020, the first day it became available. One of the major changes, a switch from the ancient nss resolver to systemd-resolved immediatelycaused me a significant amount of trouble and borked my entire network. Get the whole story and the circumvention from a 2024 perspective.
More Stories
The case of the Borked HDD
It all started this morning when I went to start my regular Saturday yoga session. I have a room at...
Beware Fedora updates of April 28, 2025
It breaks iptables with no warning I'm rather angry right now but I promise to remain calm -- at least...
Create a patch from differences in a file with the diff and patch commands
When you collaborate on a digital project with someone, it's a guarantee that eventually someone's going to need to send...
Resurrecting a Windows laptop
Recently, a friend gave me a recent model of a Hewlett-Packard Pavilion laptop. He said, “It turns on but goes...
How I recovered from another self-inflicted problem
And how I got there in the first place. Those of you who read my articles and books know that...
How to get a clean screen — on the command line
After some time using terminal sessions they can get a bit cluttered with previous commands and their output data streams....